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

Re: Subversion release planning.

From: Jani Averbach <jaa_at_jaa.iki.fi>
Date: 2005-06-19 22:45:41 CEST

On 2005-06-17 16:43-0500, kfogel@collab.net wrote:
> When some important feature is really close, we can discuss delaying
> the release, on a case-by-case basis. But we wouldn't be tempted to
> do that very often, because part of the point is to make releases more
> predictable. This is sometimes known as the "release train model".
> The idea is, trains leave the station at regular intervals. If a
> given feature doesn't make it onto this train, that's fine. The
> feature will be ready by the time the *next* train leaves, which won't
> be very long -- because we're predictable. The actual interval I'm
> shooting for is 3-4 months, though that's certainly open to
> discussion.

Do you mean by "trains" minor number, eg. 1.X.0? If so, what will be
a support time span for older versions? Let's say 1.1.x or 1.2.x
line? At one point we had this discussion, and I think that the
consensus was that version 1.(X-2) is unsupported. So, if there is a
new minor version every 3-4 months, I think that we should extend our
support period, which will, on the other hand, cause more burden for
the project.

BR, Jani

Jani Averbach
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 19 22:46:19 2005

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.