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

Re: Development practices using Subversion

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-08-06 20:02:23 CEST

"Tim Purkerson" <timp@apcon.com> wrote on 08/06/2004 01:22:55 PM:

> As our development department expands we are evaluating Subversion to be
> our SCM package. It is up and running just fine, but I am struggling
> with how to make it do the things we want it to do. So I have some
> questions.
> I am used to using labels(floating and fixed) for a software release and
> haven't been able to figure out how Subversion implements it. For
> example: If we were starting to work on release 1.2 of a product we
> would set a floating label "Release 1.2" on the latest revision of all
> of the source files. All checkouts and builds from then on would use
> this label to get the correct source file revisions. This label would
> keep moving up with each change until we made it a fixed label when we
> shipped the new release. How would we implement this with Subversion? I
> am assuming it would somehow use tags.
> Another question is how to get the release number into the application's
> about box automatically. What we would like to do is use the tag/label
> as the release number. Using the example above if a user brought up the
> about box it would say "Release 1.2". Is there a way to force this
> tag/label into a 'version.h' file when it is checked out?
> Any help would be appreciated.

PVCS VM has features like that. In my opinion, features like a floating
label exist to hide the fact that those product only offer branching on a
file by file basis. So a floating label, allows you to simulate branching
a whole project. In Subversion, you would simply make a copy of your
project to a branch folder. You would then work in the branch folder and
get the same effect. I would recommend reading chapter 4 in the book for
more information.


I do not think there are any good ways to get a release number placed in
your source code. It is possible to get the global revision number, which
can be used as a good build ID. But, to have a user-friendly value like
"Release 1.2" you would either just have to key it into a file on the
branch, or perhaps do some kind of scripting where you parse it from the
branch folder name.



Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 20:02:50 2004

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.