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

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

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-06-29 15:13:15 CEST

On Jun 29, 2005, at 2:08 AM, Robert Schneider wrote:

> So what is the BEST practice. Surely there a several
> Approaches but I would like to know the perfect one, if
> possible.

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.

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 29 15:16:57 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.