Sean Laurent <sean@neuronfarm.com> wrote on 09/23/2004 02:00:38 PM:
> On Thursday 23 September 2004 12:42 pm, Mark Phippard wrote:
> > Sean Laurent <sean@neuronfarm.com> wrote on 09/23/2004 01:32:21 PM:
> > > There's also the concept of 'labels', provided by software like
Perforce
> > > and presumably others, which has been mentioned on this list before.
> > > In Perforce, a label is simply way to reference a particular
revision...
> > > very similar to the CVS tag mechanism. I know this has been
mentioned
> > > on the list before
> >
> > To me, this is an advantage of Subversion since the global revision
number
> > is always present as a means to refer to a specific revision. You do
not
> > need to create a label to accomplish the same thing. For the same
reason,
> > you do not really even need to create a tag. The tag is a convenience
> > item for your own benefit, you do not neeed the tags to get the same
> > results from merges or other operations, as you can also just specify
the
> > equivalent revision number.
>
> Well, I have encountered one situation where labels were significantly
easier
> to use than global revision numbers. I worked in a small-medium sized
> company with about 60+ developers/QA that built shrink-wrap software. We
had
> an automated build system that created a clean build of a product,
posted it
> to a server and sent out a notification email (among a myriad of other
> things). After the build completed, the system set a label called
> 'productname_CURRENT' to point to the current revision.
>
> It was incredibly handy for developers and QA to reference the label,
instead
> of worrying about the revision number... However, this could just as
easily
> be handled by branches/tags in Subversion. The only difference, as
someone
> already pointed out, is really just the mindset ... the nomenclature.
>
Yes, this has come across the list before. The easiest thing to do is
just delete/recreate the tag.
svn delete url://server/repos/tags/productname_CURRENT -m "Refreshing tag"
svn copy url://server/repos/trunk
url://server/repos/tags/productname_CURRENT -m "Refreshing tag"
As you indicate it is the same feature with a different implementation. I
personally prefer the Subversion approach in that there is no need to
really introduce a special UI or concept for a feature that can already be
accompished. There is a consistency that is really easy to follow once
you grasp it and can set aside what you are used to from other tools.
Mark
_____________________________________________________________________________
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 Thu Sep 23 20:07:45 2004