Difference between revisions of "DevelopmentCodeline"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) m (→OpenOffice.org 3.x development code line) |
B michaelsen (Talk | contribs) m |
||
| Line 17: | Line 17: | ||
== Check-in rules == | == Check-in rules == | ||
| − | * Please follow the [[Common CheckIn Rules]] and the [[CWS_Policies]]. | + | * Please follow the [[Mercurial/Cws|CWS Workflow for Mercurial]], the [[Common CheckIn Rules|CheckIn Rules for Subversion/CVS]] and the [[CWS_Policies]]. |
* The development codeline is open until [[Feature_freeze]]. | * The development codeline is open until [[Feature_freeze]]. | ||
[[Category:Releases]] | [[Category:Releases]] | ||
Revision as of 17:31, 10 November 2009
A development codeline represents the trunk (aka HEAD) on which future releases will be developed. A CVS checkout of this branch will update the source to the latest version of the development codeline.
Examples for development codelines are:
OpenOffice.org 3.x development code line
- DEV300
- The Mercurial repository for the DEV300 codeline is available at http://hg.services.openoffice.org/hg/DEV300/ .
- The name is DEV300 on SVN HEAD, milestones of the development codeline are tagged with DEV300_mXXX, e.g. DEV300_m60 for the 60th milestone.
- These milestones can be download from http://download.openoffice.org/next.
OpenOffice.org 2.x development code line
- SRC680
- The name is SRC680 on CVS HEAD, milestones of the development codeline are tagged with SRC680_mXXX, e.g. SRC680_m218 for the 218th milestone.
Check-in rules
- Please follow the CWS Workflow for Mercurial, the CheckIn Rules for Subversion/CVS and the CWS_Policies.
- The development codeline is open until Feature_freeze.
