This is part of what caused us to be more cautious during Thanksgiving week.
We are also spending time now really looking at all the incidents we had, root causing them and figuring out how not to have it happen again. We’re working to adjust processes to catch issues earlier.
It's possible to move a tag to a different version of a file, or to remove it completely from a file.
If you update a working copy checked out to a tag, CVS will recover the appropriate versions of any files.
Care is needed, however: although it is technically possible to recover a complex map of branches using There are at least two scenarios where branches may be appropriate.
In the first case, a branch may have quite a long lifetime.
It’s 43 new features and countless bug fixes and small improvements.
That is a new record for us in a single sprint delivery.
For development projects where you're juggling several things at once, this is not only possible, it's actually pretty prudent, so I'll suggest a typical way to do this that you may want to follow.We may have marked points on that history using tags for easy recovery, but at any point in time there's only one corresponding version of each file in the project.CVS permits a more complex arrangement than this, however. Instead of a single line of history on the HEAD, we have HEAD and another branch.The information saved includes the date and time of the change, details of what exactly has changed (a (which has nothing to do with the version of the software product the file is a part of).Even when changes to a set of files are committed together, there is no logical connection between versions of files comprising a . CVS users are used to this; normally the lack of real change sets goes unnoticed.