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

Re: Things you must consider for version numbering

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-12-16 23:38:47 CET

On Tue, 2003-12-16 at 16:34, kfogel@collab.net wrote:
> (An "unstable trunk release, or snapshot" still involves a branch, of
> course, just a very short-lived one. Such releases are analogous to
> the interim releases we do right now -- 0.35, etc -- which can be
> considered snapshots from the 0.x line.)

So, right now, if we put out 0.35.0, and it has a big bug, we put out
0.35.1. What happens in your scheme when we put out 1.1.2 and it has a
big bug? Do we put out Do we put out 1.1.3 even though 1.1.3
would ordinarily come from a fresh branch?

I'm thinking, maybe we don't have to branch for unstable trunk
releases. Just tar up the trunk at a particular revision, wait a few
days or a week to make sure nobody finds any awful bugs applying to the
time you tarred up the trunk, and release the tarball. If someone did
discover an awful bug, try again as of the trunk revision the bug is
fixed on.

The above discipline is not as robust as our practice for 0.x releases,
nor is it as predictable. But it is less work and less complexity. And
unlike today, people won't need to use interim releases for real work,
and we won't be trying to put out interim releases every 2-3 weeks.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 16 23:39:27 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.