On Fri, Jul 20, 2012 at 3:21 PM, John Hunter <email@example.com>
I would like to discuss a timetable towards a python3 release (1.2 or 2.0). I'll throw this out there, and am happy to make modifications according to feedback
Aug 20th : feature freeze and branch. bugfixes only going forward from this point
Sept 15th: rc1
Oct 7th: rc2
Oct 15th release
I know we have lots of open and interesting pull requests to get in, and so if we need to push these times back to get them in that is fine. Just wanted to put something out there to see if this timeline seems plausible to people.
I think the schedule is reasonable. We are going to need significant help getting through our backlog of PRs. At the very least, we need to identify which ones are release critical or not.
Just as a note, I don't know whether or not we want to have my axes.py refactor included in this release or not. If most of my attention is going to be on the documentation and PR push, it is extremely unlikely I am going to get much further with it in the next couple of months.