[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Expected post-1.0 release cycle?

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2003-12-21 12:20:43 CET

Related to the question about what Subversion version numbers mean is what
we expect to have for a release cycle after 1.0.0. Expectations about this are
going to influence what the version number means too.

In a recent mail Greg Stein expects the release cycle to continue as it does
now; i.e. a bi-weekly release. I expect he's talking about dev builds.

Karl Fogel has expressed the expectation that there will a half year silence
after 1.0 for public (i.e. stable) releases.

I guess that to be able to address the version numbering problem, we have to
have an idea about how we are going to proceed after 1.0.0 both for dev
builds and for stable releases.

Looking at the bi-weekly dev build release cycle I think this has worked out
really great. There has been some discussion whether this should continue
after 1.0. Given our current experience we should - IMHO - at least see if it
still works after 1.0.

Seeing that frequent releases have created a level of trust of active
development and support to a wide community already, I would like to suggest we
don't hold up patch level releases too long. If there's nothing to release, then
we shouldn't, but if there is, my preference would be to release per quarter
or 4 months. Shorter intervals might interfere with active development on
other releases, although obviously attention is going to have to be devided
between public and development releases anyway.

Hoping to contribute with this mail,


+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 21 12:21:20 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.