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.
Thanks.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 19:42:53 2004