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]
