In Beehive, there's usually a branch for each release that was used for any changes before the official release and associated tag are created. When documentation "bugs" come up, we just make changes in this branch and then rebuild / repost the release's documentation.
If there isn't a branch, the tag can be used to create a branch where changes can be made as appropriate. Just don't forget to integrate those changes forward into trunk/. Works for us -- YMMV. :) Eddie On 4/21/07, sebb <[EMAIL PROTECTED]> wrote:
How do projects use SVN to manage site documentation updates for exisiting releases? When a new release is created, the site documentation and source files etc will all be in an SVN tag directory. I assume that the SVN tags should never be updated once created, so if problems are subsequently found in the site documentation, and it needs to be updated, what is a recommended way to do this in SVN? S/// --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
