Hello List,
What about getting 0.12 released this year, still? I think we can
eventually reach this goal, with multirepos nearing completion and i18n
being in a "not so bad" shape.
As discussed with Remy on IRC, we should now start to think about a
feature freeze and reduce drastically the number of tickets that can
realistically be finished for 0.12. We still have plenty of opened
tickets for 0.12, but as usual we will mercilessly move the non-critical
ones to some later milestone, like 0.12.1 for bugs and 0.13 for
enhancements (*). Also, I've started to add the "needmajor" keyword on
tickets which need some API breakage in order to be completed, meaning
they should be done for 0.12 *or* will have to wait for 0.13 or later.
So, with the above in mind, I'd like to make "official" the schedule
that Remy proposed (well, the one I remember, as the IRC archive is down
atm):
- mid of October: merge multirepos
- end of October / early November: release 0.12beta1
- November: bug fixes, last few features
- Early December: 0.12rc1
- mid or end of December: 0.12
0.11.6 could be released in parallel ("when ready"), but November sounds
right.
-- Christian
(*) before that'll happen, maybe move 0.12.1 tickets to 0.12-stable and
0.13 ones to 0.1x, for minimizing the later moves. Indeed, in the recent
past, some tickets got moved from 0.11 to 0.11.1, and from there to
every other 0.11.(i+1); let's avoid this for 0.12 by putting them on
0.12-stable and *pulling* from there for the next 0.12.i release.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
