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

Re: How to "label" correctly?

From: Michael Wood <mwood_at_its.uct.ac.za>
Date: 2002-12-24 08:02:11 CET


On Tue, Dec 24, 2002 at 12:44:12AM +0200, Roman Rytov wrote:
> > > >I found that usual labeling (tagging) doesn't exist in SVN and
> > > >actually I don't need it since I'm able to add a comment w/o
> > > >commiting all the data from my working dir. How to do it
> > > >correctly? The case is when I want to embed more meaningful info
> > > >into the branch but not merely a revision number.
> Sorry guys,
> I wrote it after a midnight and now I see it's not clear at all.
> Sorry.
> "Usual labeling" is meant to be labeling as is in VSS. I shouldn have
> not used the word "usual".
> Where may I store a release number in my source repository? It seems
> in a property file where I write a label is a right place. Correct?

I am not familiar with labeling in VSS. Using Subversion you can do
something like this:

Do your development in /trunk. When you're ready for a release, copy
/trunk to /tags/release-1.0 (which you never make changes to after
that). Then you can copy /tags/release-1.0 to /branches/stable-1.0 and
fix bugs there as they are found. New features, rewrites and other
major changes can still be made to /trunk.

Maybe encoding a release number in the name of the directory (tags and
branches in Subversion are just directories copied from somewhere else)
like this will do what you want?

It is also possible to store metadata in properties attached to files or
directories like this:

svn propset myprop "value" filename

e.g.: svn propset version "RELEASE-1.0" /branches/blah

I hope the above helps.

Michael Wood <mwood@its.uct.ac.za>
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 24 08:03:02 2002

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