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

Revision number madness

From: Jostein Chr. Andersen <jostein_at_josander.net>
Date: 2003-12-01 17:39:28 CET


I'm still thinking about handling of release numbers, this is the
situation if I make a tarball now:

If we look at /trunk/CHANGES the beginning is:

  Version 0.34.0 (released 3 December 2003, from revision r7859)

If nothing happends in trunk (as the time of writing), then I commit
CHANGES and svn_version.h as revision 7894 and start to make the tarball
with help of
 $ ./dist.sh 0.34.0 7894

What do svn --version say after compiling? It says:
  svn, version 0.34.0 (r7894)

So, it will be a big gap between the branched release and the revision
number on the exe.

My suggestion is that I:

* Merge CHANGES and svn_version.h into branches/0.34.0 (r7894)
* Make the header in CHANGES say:

  Version 0.34.0 (released 3 December 2003, from revision r7859)
  http://svn.collab.net/repos/svn/tags/0.34.0 r7895

  And commit before anybody else are doing something.

Then I do
  $ ./dist.sh 0.34.0 7895

And tests the tarball. The shiny new svn --version should be:
  svn, version 0.34.0 (r7895)

. If everything is fine, then I merges CHANGES from branches/0.34.0 into
the trunk and move branches/0.34.0 to tags/0.34.0 and release the



http://www.josander.net/kontakt/ ||
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 1 17:42:17 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.