Hugo Heden <heden@foi.se> writes:
> In May 2004 I posed a question on this list about "labeling"
> functionality "for the typical project manager" (as opposed to regular
> svn-tagging, see below), see
> http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=10537
> for an archive view of that message, and now I would like to ask again.
>
> At that time the response was that this feature had been discussed at
> length on the dev-list ("Revision Indexes") .. "wait and
> see". However, looking at the roadmap,
> http://subversion.tigris.org/roadmap.html, there does not seem to be
> any plans to introduce such functionality in the near future.
>
> What is the current status on this?
>
> The question follows in part below (copy-pasted from the May 2004-message).
The same, I think: "No action planned." It seems that no developer
finds this compelling enough to implement, or review in depth. Sorry,
I know that's not the answer you were looking for. I personally would
rather see it implemented as a wrapper around Subversion, than as a
native feature. Your team could just keep a text file mapping labels
to revisions, for example, and then have a script that parses the file
and does the requested Subversion operation.
The set of developers changes over time (to see how, post patches! :-) ),
so this response might be different someday, of course.
Best,
-Karl
> <snip>
> Good day all,
>
> I am in trouble. I have convinced my project managers that we should
> try out Subversion in a project. It all works fine, especially for
> the programmers. The "trunk-tags-branches-model" works excellent for
> us when working on the source code tree.
>
> However, the project managers keep asking about certain functionality
> (see below), and I can't figure out what to tell them.
>
> I am considering to file this as an RFE, but I assume other people
> have encountered this as well. How do you people "out there" solve the
> following problem?
>
> ==================
>
> Here we go. People (our project managers) would like to be able to do
> (something similar to) the following:
>
> 1) Enter some directory in the (trunk of the) project tree, where some
> document (currently of interest) resides:
>
> % cd /home/myname/myproj/Requirements/UseCaseDoc
> % ls
> doc.tex image.gif makefile 2a) Set an (unversioned) textual "label"
> (or "alias" or "tag") for any
> given repository revision number -- for any item in the tree (a
> directory or a file). In effect, such a "label" would work as a
> *textual alias* for the repository revision number, an alias that is
> "in scope" for a certain item only -- not the whole repository. I have
> invented some mock svn-subcommands to illustrate. For example:
>
> % svn status -u
> Status against revision: 354
>
> % svn labelset "VERSION 0.2.0" -m "after first review meeting" .
> Setting label "VERSION 0.2.0" on revision 354 of directory "."
>
> % svn labelset -r201 "VERSION 0.1.9" -m "performed spellcheck" .
> Setting label "VERSION 0.1.9" on revision 201 of directory "."
>
> 2b) For any given item (file or directory), list the (whole)
> "label-history" of the item. % svn labellist .
> rev label comment
> ---- ------------- ----------------
> r354 -- VERSION 0.2.0 -- after first review meeting
> r201 -- VERSION 0.1.9 -- performed spellcheck
> r121 -- VERSION 0.1.0 -- initial version
>
>
> 2c) Use the label (just as with ordinary repository revision numbers)
> to do svn update:
>
> % svn update --label "VERSION 0.1.9" .
> U doc.tex
> U image.gif
> U makefile
> Updated to revision 201, with label "VERSION 0.1.9".
>
> ====================
> </snip>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 14 19:12:46 2005