Pierre Asselin wrote:
My advice: tag when you ship and don't bother tagging anything else. Exception: you should maintain a "moving tag" when you merge your bug fixes to the trunk, like this:
Tags can be useful also when you have made a significant change to the code base, and want to tag the "before" snapshot just in case you've screwed up big-time in your check-in. Of course, if you have a comprehensive set of unit tests, this becomes less of an issue ;=)
I'd suggest not being shy with tags - they're easy enough to remove (if you really need to) but a pain to apply after the fact.
-- Jim _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
