-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove legacymode? #40
Comments
Perhaps add something to the readme specifying that version X and under support legacy mode, but everything after does not. Thoughts? |
Agreed. Current version is 1.4. I propose releasing 1.4.1 with the current set of recent changes. Then remove legacy mode and bump version to 1.5 with legacy mode removed. Removal of legacy mode could then coincide nicely with move to the new project name and distribution on pypi. |
Sounds good! |
Cool. Will you be managing the process of removing legacy and bumping the version and letting Nathan know i #28 that we're ready for PyPi? Or did you want us to do that? |
Good question. I'd be happy if you guys took over! |
Hi
I have started the unit tests, and then become bogged down in trying to create a Library.XML file that works properly. That will just have to wait.
Configuring a Traveis CI build and adding to PyPi can be done when you are ready.
Regards
Nathan
… On 14 May 2017, at 18:27, Liam Kaufman ***@***.***> wrote:
Good question. I'd be happy if you guys took over!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Just curious how long you want to support legacymode? We could remove a fair bit of clutter without it.
The text was updated successfully, but these errors were encountered: