as an example, the scheme I've been tinkering with looks something like
this:
/tags/dev -> write access to *, meant for (temporary) tagging by developers.
They'll create a tag, tell me what it is and I'll move it to one of the
other locations. This allows me to enforce naming standards etc while at the
same time not overly restricting developers' freedom of movement in getting
the job done. I imagine for the most part I'll be trying to get developers
to use the "fixed in r1234" model.
/tags/tickets/ticketA/revision0
/tags/ticket/ticketB/revision0
/tags/ticket/ticketB/revision1
etc ... -> write access to @admin, meant for tagging
change/enhancement-request/bugfix-related work
/tags/projects/projectA
/tags/projects/projectB
etc ... -> write access to @admin, meant for tagging project-related work
/tags/archive -> write access to @admin, meant for archiving tags that we
want to preserve conveniently, but are no longer used actively.
I'll svn rm entries from /tags/archive that haven't been touched for a
specified amount of time.
pretty much the same for /branches
This theoretically allows us to keep everything around that we might need
quickly, and the versioned rm's allow me to dig anything up from the bowels
of SVN that I thought I was never going to have to touch ever again ...
Hope this helps ...
Rob
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Friday, March 05, 2004 11:19 AM
> To: TBrowder
> Cc: users@subversion.tigris.org
> Subject: Re: Re: Wish List (Revisited)
>
>
> On Thu, 2004-03-04 at 18:14, TBrowder wrote:
>
> > The history -T from CVS gives a date-sorted list of tags
> associated with a
> > module. It's invaluable when we need to see a history
> point when a product
> > went out the door. And we can retrieve its state at that
> point by the tag
> > name. (And it can't be easily changed.) I want to do the
> same thing with
> > subversion. I don't care to see the directory tree
> polluted with lots of
> > names just to have tags at milestones.
>
> I don't understand why you can't do this in SVN.
>
> Run 'svn ls -v' on a directory URL containing tags. You'll see the
> exact date each tag directory was created.
>
> If you don't want 10,000 tag directories all in the /tags area, then
> make up your own organizational system. Create any sort of
> subdirectory
> structure you want to organize your tag directories: group them by
> month, or by product, module, whatever.
>
>
> ---------------------------------------------------------------------
> 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 Mar 5 19:03:16 2004