Change Control |
Discussion: A development project will generally be divided into logical tasks, for example, fixing a particular bug in a software project or adding a web page to a web site project. Often you will want to be able to track such tasks, or "changes", through a development process. Later you may wish to see the history of what was modified as part of each change. Some aspects of change control can be handled completely outside CVS using a tracking system such as GNATS or Jitterbug. One way to connect such a system to CVS is to require CVS log messages to contain a valid bug number. For details, see the CVS documentation for the "verifymsg" feature of CVS. If you would like CVS to remember that checkins to several files were made as part of the same logical change, create a tag before and after each checkin (generally via some kind of custom front-end to CVS). |
Return to The Information Page List.
![[ Valid XHTML 1.0! ]](/branding/w3c-valid-xhtml10-44x16.png)
![[ Valid CSS! ]](/branding/w3c-valid-css-44x16.png)
