> -----Original Message-----
> From: Dan Crosta [mailto:email@example.com]
> Sent: Friday, September 29, 2006 4:02 PM
> To: Reedick, Andrew
> Cc: firstname.lastname@example.org
> Subject: Re: updating a tag
> OK, that's what I figured... "floating label" sounds like about what I
> was looking for.
> Do people not generally use tags for maintenance to already-released
> versions? Or is that ordinarily done with branches? (I'm still a
> little unclear on the best practices and conventions surrounding those
> For my stuff, I'll stick with the rm/cp method, or really just not
> tagging a version until I'm sure I'm done with it :-)
Maintenance should be done on it's own branch. The maintenance branch
should branch from the tag.
Working directly on the tag is bad because:
- the tag is supposed to be a known baseline. By developing in
the tag, anyone who tries to use the tag gets random code. Random code
is bad, but only because customers don't like paying for random code,
which makes it difficult for your company to pay you.
- if you start a patch in the tag, what do you do when a 2nd
more critical tag needs to go out first?
- tags exist to help make branching or research easier. If I
see tags/prod.1.0, I expect it to be 1.0, not 1.0 plus two maintenance
- if you do update a tag, you're morally, legally, and ethically
obligated to warn everyone that if they checked out the tag previous to
your change, they need to run 'svn update', or worse, re-do and
re-deliver their work to pick your change.
You might want to look at the tools/contributed software and see about
limiting write access to the tags directory.
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA622
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 29 22:21:18 2006