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

AW: Is there an ultimate solution for the build process/global revision number

From: Robert Schneider <r.schneider_at_weingartner.com>
Date: 2005-06-30 13:10:01 CEST

Hi Ben and all that have replied,

I think this is the ultimate answer which has opened my eyes:

> <recording>
> The global revision number is NOT an indicator of the maturity of
> your software. It's just a global counter, something which names
> commits and marks off points in time. Because branches and tags live
> as ordinary directories along side the trunk, saying "I have r29382
> of the software" does not mean anything.
> </recording>
> The BEST practice is to do normal software release management
> procedures, ones that are used on all version control systems:
> 1. invent a a release numbering system that works best for you,
> something like "version 1.0, 1.1, ...", etc.
> 2. create release branches. tag releases. This is all described
> in the book at http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-
> ch-4-sect-4.4 .
> The global revision number has nothing to do with this best practice.

Since the question about revision numbers and including them into source
code has appeared often I was seduced to do it the same way. And I guess
(since I saw it in other applications) that other do include the
number, but probably without any advantages. Or maybe with other version
systems it makes more sense.

Thank you all,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 30 14:05:37 2005

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

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