Difference between revisions of "DevelopmentCodeline"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (OpenOffice.org 3.x development code line)
m
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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.
+
A development codeline represents the trunk (aka HEAD) on which future releases will be developed. A [[Mercurial]] (HG) checkout of this branch will update the source to the latest version of the development codeline.
  
 
Examples for development codelines are:
 
Examples for development codelines are:
Line 6: Line 6:
  
 
* DEV300
 
* 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.
+
: The HG repository for the DEV300 codeline is available at http://hg.services.openoffice.org/hg/DEV300/ .
: These milestones can be download from http://download.openoffice.org/next.
+
: The name is DEV300 on HG HEAD, milestones of the development codeline are tagged with DEV300_mXX, e.g. DEV300m80 for the 80th milestone.
 +
: These milestones can be download as [http://download.openoffice.org/next Developer Snapshots].
  
 
== [[OpenOffice.org]] 2.x development code line ==
 
== [[OpenOffice.org]] 2.x development code line ==
  
 
* SRC680
 
* 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.
+
: The name is SRC680 on [[CVS]] HEAD, milestones of the development codeline are tagged with SRC680_mXX, e.g. SRC680_m218 for the 218th milestone.
  
 
== 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]]

Latest revision as of 11:50, 13 December 2010

A development codeline represents the trunk (aka HEAD) on which future releases will be developed. A Mercurial (HG) 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 HG repository for the DEV300 codeline is available at http://hg.services.openoffice.org/hg/DEV300/ .
The name is DEV300 on HG HEAD, milestones of the development codeline are tagged with DEV300_mXX, e.g. DEV300m80 for the 80th milestone.
These milestones can be download as Developer Snapshots.

OpenOffice.org 2.x development code line

  • SRC680
The name is SRC680 on CVS HEAD, milestones of the development codeline are tagged with SRC680_mXX, e.g. SRC680_m218 for the 218th milestone.

Check-in rules

Personal tools