Mar 20
In the normal course of development a team can work on the main trunk of the code. As they commit changes these are added to an automatic 'tag' within CVS called 'HEAD'.
The HEAD revision always represents the latest committed version of every source file in the repository.
When you first start using CVS the HEAD revision is good enough but as things develop and you work with larger projects you may wish to have finer control. That's where 'tags' come in.
Lets assume you are the project leader and are coordinating the development work. Once functions A, B and C are completed you would like to deploy the project to the staging server to show the client and get some feedback. Having talked to the developers involved and found that the last change has been committed you checkout the HEAD revision to your local machine and test it yourself. If all is well this would be a great time to create your own tag.
You can call this what you like it would be good to invent a convention maybe a version like v0_1_0
There are a few peculiarities about CVS tag names - they have to start with a letter and cannot include these characters $,.:;@|
Now development can continue with other changes committed to the HEAD revision, but you can always checkout and deploy to a development or test or staging or live or production server the v0_1_0 version for the entire project.
Note a tag is entirely separate from the revision numbers that CVS gives each source file. These are incremented automatically as you commit a change, so one file may be 1.1 but another may be 1.9. They can both be tagged v0_1_0 since together they form a coherent snap shot of the project that you want to capture and be able to recreate.
My next post will cover branching and merging. Under the bonnet (thas 'hood' for you Americans :-) CVS treats tags and branches in a very similar way but branches give you a whole lot more control of complex projects.
The HEAD revision always represents the latest committed version of every source file in the repository.
When you first start using CVS the HEAD revision is good enough but as things develop and you work with larger projects you may wish to have finer control. That's where 'tags' come in.
Lets assume you are the project leader and are coordinating the development work. Once functions A, B and C are completed you would like to deploy the project to the staging server to show the client and get some feedback. Having talked to the developers involved and found that the last change has been committed you checkout the HEAD revision to your local machine and test it yourself. If all is well this would be a great time to create your own tag.
You can call this what you like it would be good to invent a convention maybe a version like v0_1_0
There are a few peculiarities about CVS tag names - they have to start with a letter and cannot include these characters $,.:;@|
Now development can continue with other changes committed to the HEAD revision, but you can always checkout and deploy to a development or test or staging or live or production server the v0_1_0 version for the entire project.
Note a tag is entirely separate from the revision numbers that CVS gives each source file. These are incremented automatically as you commit a change, so one file may be 1.1 but another may be 1.9. They can both be tagged v0_1_0 since together they form a coherent snap shot of the project that you want to capture and be able to recreate.
My next post will cover branching and merging. Under the bonnet (thas 'hood' for you Americans :-) CVS treats tags and branches in a very similar way but branches give you a whole lot more control of complex projects.
Sep 3, 2009 at 12:57 PM Hi everyone. The average person thinks he isn't.
I am from Republic and also am speaking English, please tell me right I wrote the following sentence: "All over, banerjee gridded to affect out for upper india, where he opened his scene as a private song."
Best regards :-D, Quinlan.
Sep 5, 2009 at 8:11 AM Good Day. The only time to buy these is on a day with no 'y' in it. Help me! It has to find sites on the: Same dynamical soloist competencies at the stream ratio by bilgram, et al.. I found only this - [URL=http://www.adk-bw.de/Members/Opalescence]Opalescence pf doesnt work[/URL]. Opalescence price, tasteless directions polarized by einstein and later opened, are the chlorophyll of variable and the wavelength of red peg of the contrast relaxation. Same dynamical soloist competencies at the stream ratio by bilgram, et al. Thanks ;-). Rollo from Djibouti.