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

RE: Re: Similating "label" feature in Subversion?

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-08-27 19:22:33 CEST

> -----Original Message-----
> From: Jean-Claude Antonio [mailto:jcantonio@arcetis.com]
> Sent: Sunday, August 26, 2007 9:38 AM
> To: fj
> Cc: users@subversion.tigris.org
> Subject: Re: Similating "label" feature in Subversion?
>
> Hello David,
>
> I am not sure I understand this specific issue, as you can
> always get the specific "label" (r31).
> Would svn export|co -r31 ... solve the problem?
> Also in svn tags should not be modified as opposed to
> branches (you can write scripts if needed).
> Cheers,
>
> *Jean-Claude Antonio*
> Responsable Méthodes/Outils
> Arcetis,
> VoilaSVN Subversion Search Engine
> Tél: +33 (0)6 09 13 15 63 - Fax: +33 (0)9 59 18 24 38
> Mél: jcantonio@arcetis.com
> www.arcetis.com
>
>
>
> fj a écrit :
> >
> > Bicking, David (HHoldings, IT) wrote:
> >> I have an interesting situation where labels (rather than "tags")
> >> would be handy. I want to identify a certain revision (r31) as a
> >> suitable rollback point during testing. Since we're testing the
> >> functionality of Subversion, we don't really care about
> the revisions
> >> after this stable starting point. We care about whether
> the behavior
> >> is as expected, and we might want to rollback all changes
> to r31 to start fresh.
> >>
> >> Now, this is just the current need. I can forsee where we
> might want
> >> to identify particular revisions for the future. For example "We
> >> created branch XYZ at this revision". Of course, these
> labels would
> >> have to be something we can easilly see with a report or
> by looking
> >> at a property history on the repository.
> >>
> >> Do any of you know an efficient way to get this functionality? I
> >> took a quick stab at creating a custom property called
> "label" but it
> >> doesn't seem to be what I need. When I update it, the original is
> >> then hidden in history and I can't really find it in a repository
> >> browser or a property list in my workspace.
> >>
> >>
> >> --
> >> David Bicking
> >>
> >>
> >>
> *********************************************************************
> >> ****
> >>
> >> This communication, including attachments, is for the
> exclusive use
> >> of addressee and may contain proprietary, confidential and/or
> >> privileged information. If you are not the intended
> recipient, any
> >> use, copying, disclosure, dissemination or distribution is
> strictly
> >> prohibited. If you are not the intended recipient, please
> notify the
> >> sender immediately by return e-mail, delete this communication and
> >> destroy all copies.
> >>
> *********************************************************************
> >> ****
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> >> For additional commands, e-mail: users-help@subversion.tigris.org
> >>
> >>
> > for what it's worth, I second the idea (as i have in previous
> > messages) of implementing a real label feature in svn.
> >
> > I was a StarTeam administrator for 6 years, as well as being the qa
> > director, primary software config. mgmt. authority, and I
> think I also
> > washed a few bottles every now and then at that same gig. With
> > StarTeam, we used their view-level and rev-level labeling feature
> > extensively; it is quite powerful. I don't want to run-on about it,
> > but if anybody has any questions about it I'll certainly try to
> > elaborate. My point is, labeling, done well, can indeed be a very
> > useful capability.
> >
> > Don't get me wrong -- SVN's a great tool, especially for the price
> > (StarTeam cost a stunningly large amount of money for the number of
> > licenses the organization owned), and I'm generally agnostic about
> > tools -- use what I have to, use what I've got, etc., and
> figure out
> > how to make it work. Part of the ex-military in me... but
> I do miss
> > some of StarTeam's features, and a true labeling capability like
> > StarTeam has is one of those features I miss.
> >
> > cheers,
> > fj
> >

Thank you for your reply. What you suggest is to use the revision. However, I am talking about labeling a revision with a human-readable, searchable text fragment. Some SCM tools permit labels on individual files at specific revisions, though these systems usually keep revisions per file, not per repository.

Thus, on mainline, we would be able to get a list of all labels on the XYZ folder (which is a whole application project) that might look like this:

Branch: 2007-05-01; Mini-effort on feature A
Merge: 2007-05-04; Mini-effort on feature A completed
Branch: 2007-05-15; Mini-effort on feature B
Merge: 2007-05-04; Mini-effort on feature B completed
Rollback Point: 2007-04-04; This is a safe rollback point during development of feature X.

The above is an example in which I can identify a sort of timeline of development. In the last example, I might have placed that there on the project because we're going to try something particularly experimental over a period of days and want to easily see which revision represents the last good place. Of course, branches could be used for that purpose, too. In some other SCM tools, a rollback to a revision or label results in the elimination of all revisions of the flagged files after that point. I realize that is not the case with Subversion.

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 27 19:24:13 2007

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