RE: Roadmap for 1.1

This is in response to both kfogel and maxb:

In our workshop labels are applied to a specific revision in an archived file. Labels can be reassigned, can float to the default revision (the tip) or stick to a specific revision. They can be assigned to all files, to those with a particular criteria, or to one file. Older files in our system may have many labels because we've been doing it this way for two years. We do our builds by 'getting' a label.

When you look at the file you have access to all labels. It has been helpful in diffing revisions to an archive because they aren't in different folders, as cheap copies would be. While I'm pretty new to configuration management it makes sense to me that the entire history of an archive, including how it has been labelled, belongs in one place. I may be wrong, or it may just be a matter of individual preference or workshop procedure. I know that Subversion tagging will allow us to see the differences between revisions, but finding those revisions will take more time than just clicking on an archive and scrolling down the label list.

Regarding locking: While it may very likely be a part of the 1.1 roadmap, I'm being pressed for details by my boss, who wants to switch to something else. Without having a schedule I'm having to defend not switching to VSS from PVCS. Maybe this isn't the correct forum to discuss that. We're already being pulled into .Net, and if we go to VSS then I might as well give up any non-Windows tools at all. That is a demoralizing thought.

Please understand that I am not criticizing Subversion or the work that has gone into it. I looked at everything I could find, open source and proprietary, and chose Subversion as our alternative because it is a great tool. Even the most critical developers on the team I support have been impressed with it. I'm trying to learn Linux and Apache just for Subversion.

Thank you,

Chris Estes
Configuration Manager
Nexus Systems, Inc.

-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net]On
Behalf Of kfogel@collab.net
Sent: Friday, April 02, 2004 8:03 AM
To: Chris Estes
Cc: users@subversion.tigris.org
Subject: Re: Roadmap for 1.1

"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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 17:38:26 2004