This is not final; I'm still editing it. Please come back later. -- Nick
= Tor 0.2.3: roadmap, timeline, vague priorities. =
This is Nick's vague draft plan for a Tor 0.2.3.x release.
'''Please don't edit it without talking to me first:''' I've made a section at the bottom of the page for that.
== Timeline ==
(All dates subject to change if there's a
December 1: '''Big patch freeze.''' No new big patches get merged after this date.
January 6: '''Feature freeze.''' No features after this date. Bugfixes are limited to regressions against 0.2.2, serious bugs usability/security/reliability bugs, and bugs which for whatever reason can't wait for 0.2.4.x.
When it's done, hopefully by the end of Feb: '''Release.'''
The definition of "big patch" is deliberately vague.
Note that the cutoffs above are merge freezes, not submission freezes. If you give me a big patch on December 1, and I can't merge it on that day (because of time, or because it needs changes, or for whatever reason), it will have to wait. Thus, if there's something big that you want to have put into 0.2.3.x, then you should try to get it into the review pipeline well before the merge cutoff.
== Priorities ==
Here is a rough list of my current priorities for 0.2.3.x. Note that this list involves more items than we will have time to do; some things will get bumped.
Again, please don't edit this without talking to me.
THIS IS NOT DONE YET; I WILL EDIT MORE.
The old version of this list was features. This is must-fix bugs. All other bugs in the 0.2.3.x milestone are good-to-fix if possible.
TODO:
* Merge stuff in needs-review. Stuff in needs-review as of 16 May is not on this list.
* Go through stuff in needs-information. Stuff in needs-info as of 16 May is not on this list.
* Get all "new"/"accepted"/"assigned" 0.2.2 items done. Stuff in 0.2.2 is not on this list.