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

Re: version numbering

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-12-16 21:25:12 CET

On Tue, 2003-12-16 at 15:19, John Peacock wrote:
> > Clearer, but contrary to what you said before, the version number does
> > not indicate what branch a build is from; 1.1.1 was made from trunk
> > while 1.1.42 was made for the 1.2 stabilization branch.
> 1.1.1 was branched from the trunk prior to release, yes. 1.1.42 was the last
> version released, so that will be will be reported (plus the revision number).
> The fact that eventually this branch may be used to cut 1.2.0 is besides the point.

You seem to be missing a key phase of the release process. Before we
cut 1.2.0, we will branch for 4-8 weeks. We will be making testing
tarballs from that branch perhaps every two weeks. What version numbers
will these tarballs have?

> > You have also left out what "svn --version" displays for a private build
> > made from the trunk after we have branched for 1.2 (but before we have
> > released 1.2).
> It will still display 1.1.42 [or whatever was the last release before 1.2.0 was
> cut] (plus the revision number), since 1.2.0 doesn't exist until 1.2.0 is
> released. The fact that in the repository there is a tag called "1.2.0" doesn't
> mean anything until it is released. We have to trust people not to update to
> the 1.2.0 tag until after we have officially released it (although, by 1.2.0 we
> will have ACL's to enforce that, right?).

So, it doesn't bother you that 1.1.42 (rXXXX) might contain significant
trunk changes not present in 1.2.0, even though 1.2.0 is a greater
version number than 1.1.42?

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