Current plan for Phoenix
Robin Dunn <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi all, It's been a long while since I've written any kind of roadmap for Phoenix, so here is one. There's not much detail (and no dates!) but I thought it would be good to let everybody know what direction I am headed. 1. Alpha release: This will basically be what is in the current snapshots, and will mainly be a test of the start to finish release process, including building release binaries on the buildbot, digitally signing the wheel files, uploading to PyPI, etc. and it is almost ready to go now. (See other email about the name...) 2. Bug fixing: After any kinks found in the build and release process have been ironed out I intend to focus again on bug fixing and other polishing of the project in the lib, docs, demo and etc. This is an area where it is easy to incorporate fixes from others so if you've been meaning to look into solving some Phoenix or Py3 issues in the wx.lib, or have been sitting on some fixes you've already made, then please get them submitted as PRs. This effort will likely result in some beta builds, published on PyPI, or perhaps we'll just jump to the release candidate stage, depending on how things go. 3. Official release: The first official release of Phoenix will be published on PyPI and will be based on the wxWidgets 3.0 branch. I'm not shooting for a perfect release here, but rather an "almost everything works" and "applications using Classic can be ported with small to moderate effort" kind of release. 4. Post-release focus: My intent is to then switch my focus over to the wxWidgets 3.1 branch and get all the new stuff added to Phoenix, with regular pre-release builds (beta and/or rc). The main intent here is to get caught up to wxWidgets and stay more in-sync with them. Since Phoenix has less dependency on official wxWidgets releases, I expect to be able to make official releases of Phoenix whenever it makes sense to do so. 5. I have no plans for working on continued releases for Classic. I expect that there are some folks who would prefer to see a Classic wxPython for wxWidgets 3.1 instead of just a Phoenix version, but without Py3 support the value of that option is dwindling fast IMO. -- Robin Dunn Software Craftsman http://wxPython.org -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.