To answer the original question, the logic seems to be as follows:
- For a major new feature, or if a year has passed, update x.
- If we know of a significant feature that's going to be merged in
ahead of time, update y.
- Otherwise, update z.
- Bugfix only, release x.y.z.w.
Anyone is welcome to release/maintain a bugfix only Sage at any time,
but unless its critical the people who actually do release managements
decide putting out new features is a better use of their time. There
are pros and cons to the "release early, release often" way of doing
things, but this has been discussed on this thread and many others,
and I don't see our frequency or content of releases changing unless
the (volunteer) developer and release community changes.
I agree that there's lots of room for improvement in deciding whether
x or y should be updated, but the difficulty (both socially and
technically) is that a release is usually named before it is decided
what to put into it.
- Robert
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
