Difference between revisions of "ReleaseCodeline"
From Apache OpenOffice Wiki
m (remove redirect) |
|||
| Line 3: | Line 3: | ||
Examples for a [[ReleaseCodeline]] are : | Examples for a [[ReleaseCodeline]] are : | ||
| − | + | == [[OpenOffice.org]] 2.x release code lines == | |
| + | * OOF680 | ||
| + | : OOF680 is the release code line for the OpenOffice.org 2.2.x line. The CVS branch tag is mws_oof680, milestone are tagged with OOF680_mXX, e.g. OOF680_m14 for the actual 2.2.0 release. | ||
| + | : the naming convention for future codeline is to use the 3rd letter in OOX680 is alphabetical order, e.g. the name of 2.3 release will be OOG680. | ||
| − | + | == [[OpenOffice.org]] 1.1.x == | |
| − | + | * branch tag for 1.1.x codeline was mws_srx645 | |
| + | |||
| + | == [[OpenOffice.org]] 1.0.x == | ||
| + | |||
| + | * branch tag for 1.0.x codeline was mws_srx644 | ||
Revision as of 10:26, 27 July 2007
A ReleaseCodeline represents a branch on which a Product Release has been developed. A CVS checkout of this branch will update the source to the latest version of the Product Release.
Examples for a ReleaseCodeline are :
OpenOffice.org 2.x release code lines
- OOF680
- OOF680 is the release code line for the OpenOffice.org 2.2.x line. The CVS branch tag is mws_oof680, milestone are tagged with OOF680_mXX, e.g. OOF680_m14 for the actual 2.2.0 release.
- the naming convention for future codeline is to use the 3rd letter in OOX680 is alphabetical order, e.g. the name of 2.3 release will be OOG680.
OpenOffice.org 1.1.x
- branch tag for 1.1.x codeline was mws_srx645
OpenOffice.org 1.0.x
- branch tag for 1.0.x codeline was mws_srx644
