Hello,
As we have a good deal of useful fixes in 0.12-stable, we can think
about making a 0.12.1 release. Not to mention the fact that the 13th of
September, we'll be 3 months after the 0.12 release, a good timing.
So let us know if there's something important which is still missing.
Also, most probably not all of the 15 tickets still scheduled for 0.12.1
will make it.
I'd say we can enter a string freeze of one week after this week-end,
followed by a 0.12.1rc1 release candidate (so approximately the 13th).
After the usual one week of intensive testing, if everything is fine
(e.g. no Python 2.4 breakage for example...), we'll do the actual release.
As a side-note, we dropped the idea of doing a last 0.11.7.1 or 0.11.8
release. Focus should rapidly shift toward the new stuff for 0.13, and
doing 0.12-stable maintenance releases is enough of a burden ;-)
Of course, if someone else has enough interest in continuing the
maintenance of 0.11-stable and has the proper experience to do so, he
would be welcomed.
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
