Hello list,
We're pretty much good to go for a release candidate, which we'll do
Friday evening. Only translation and documentation updates should go in
after that, for a short period of time (let's say 1 week) before we
release 1.0 itself (that means Sept. 7).
At this point we're switching to our new version numbering scheme, with
frequent releases for both stable (1.0.x) and dev (1.1.x), approximately
as often as there's cool new stuff going in ;-)
Releases for 0.12.x will be less frequent. I think we're going to cut a
0.12.4rc1 as well tomorrow evening, and release 0.12.4 at the same time
as 1.0. After that, I think we're only going to have releases for
critical issues there (i.e. data loss or security related), unless
someone steps up to be a dedicated maintainer. In any case, there will
be no more new features for 0.12.x.
This raises the question of the policy on 1.0.x about new features: I
think we can keep our usual way, with the early maintenance releases
still getting a few non-disruptive improvements, while the later
releases will only get bug fixes.
The real change with the new release policy will be that for the
*disrupting* and important new features, people will not have to wait 2
years before getting their hand on a release!
-- Christian
--
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.
