kfogel@newton.ch.collab.net wrote on 04/02/2004 08:02:35 AM:
> "Chris Estes" <cestes@nexussystems.com> writes:
> > I work for a shop that is using PVCS Version Manager and the entire
> > development team refuses to switch from our expensive system to
> > Subversion without locking. Labels are an integral part of our build
> > system. I have my team lead asking me when Subversion will have
> > locking, and I have developers griping about PVCS, but I can't
> > switch them to PVCS until the features Mr. Nicholls lists are in
> > Subversion. We are drifting towards other solutions (VSS, mainly)
> > and I'm trying to hold back the tide. A definite roadmap that
> > includes locking and labels would be a great help in actually
> > TURNING that tide.
>
> We've heard from a few people that "labels" are crucial. Usually, we
> svn developers get confused, and say "But we have labels -- our cheap
> copies are the same as labels!"
>
> Now I'm getting the feeling that "labels" doesn't mean the same thing
> to all people :-). Could you describe in some detail what they mean
> to you and how you use them? Some concrete examples would be
> great.
>
> Thanks,
> -Karl
>
I often use labels in PVCS to store things like a bug number assoicated
with the change. My plan for this in Subversion was to use properties,
which I think is a potentially better solution anyway since I can name the
property something meaningful that describes what the value means, where
in PVCS I have some labels that are to tag versions and other that are bug
numbers.
One potential problem with this approach in Subversion is that I am not
sure if properties are meant for this. For example, is there anyway to
ask Subversion for all of the file revisions that contain a ceratain
property value such as issue=1234?
Thanks
Mark
Received on Fri Apr 2 17:04:15 2004