ReleaseCodeline

A release codeline represents a branch on which a Product Release has been developed. A checkout of this branch will update the source to the latest version of the Product Release.

OpenOffice.org 3.x release code lines

• OOO3X0
  • OOO330 as release code line for the OpenOffice.org 3.3.x release. The HG branch is OOO330. Milestones are tagged with OOO330_mXX.
  • OOO320 as release code line for the OpenOffice.org 3.2.x release. The HG branch is OOO320. Milestones are tagged with OOO320_mXX (e.g., OOO320_m12 for the 3.2.0 release).
  • OOO310 as release code line for the OpenOffice.org 3.1.x release. The CVS branch is OOO310. Milestones are tagged with OOO310_mXX (e.g., OOO310_m11 for the 3.1.0 release).
  • OOO300 as release code line for the OpenOffice.org 3.0.x release. The CVS branch is OOO300. Milestones are tagged with OOO300_mXX (e.g., OOO300_m9 for the 3.0.0 release).

The naming convention for future release codelines is to use the 5th character in OOO300 in numerical order.

The release codeline will be used for 2 releases. The first release is a feature release and the second is a bugfix release (e.g., OOO310_m11 for 3.1.0 and OOO310_m19 for 3.1.1).

The milestones towards the final release can be download as Developer Snapshots.

The milestones short before the final release can be download as Beta or Release Candidate.

OpenOffice.org 2.x release code lines

• OOX680
  • OOH680 as release code line for the OpenOffice.org 2.4.x releases. The CVS branch tag is mws_ooh680, milestone are tagged with OOH680_mXX, e.g. OOH680_m12 for the 2.4.0 release.
  • OOG680 as release code line for the OpenOffice.org 2.3.x releases. The CVS branch tag is mws_oog680, milestone are tagged with OOG680_mXX, e.g. OOG680_m5 for the 2.3.0 release.
  • OOF680 as release code line for the OpenOffice.org 2.2.x releases. The CVS branch tag is mws_oof680, milestone are tagged with OOF680_mXX, e.g. OOF680_m14 for the 2.2.0 release.
  • OOE680 as release code line for the OpenOffice.org 2.1.x releases. The CVS branch tag is mws_ooe680, milestone are tagged with OOE680_mXX, e.g. OOE680_m6 for the 2.1.0 release.
  • OOD680 as release code line for the OpenOffice.org 2.0.4 release. The CVS branch tag is mws_ood680, milestone are tagged with OOD680_mXX, e.g. OOD680_m5 for the 2.0.4 release.
  • OOC680 as release code line for the OpenOffice.org 2.0.3 release. The CVS branch tag is mws_ooc680, milestone are tagged with OOC680_mXX, e.g. OOC680_m5 for the 2.0.3 release.
  • OOB680 as release code line for the OpenOffice.org 2.0.2 release. The CVS branch tag is mws_oob680, milestone are tagged with OOB680_mXX, e.g. OOB680_m5 for the 2.0.2 release.
  • OOA680 as release code line for the OpenOffice.org 2.0.1 release. The CVS branch tag is mws_ooa680, milestone are tagged with OOA680_mXX, e.g. OOA680_m145 for the 2.0.1 release.
  • OOO680 as release code line for the OpenOffice.org 2.0.0 release. The CVS branch tag is mws_ooo680, milestone are tagged with OOO680_mXX, e.g. OOO680_m124 for the 2.0.0 release.

The naming convention for future release codelines is to use the 3rd letter in OOX680 in alphabetical order, e.g. the name for the 2.3 release will be OOG680.

OpenOffice.org 1.1.x

• mws_srx645 as branch tag for 1.1.x codeline

OpenOffice.org 1.0.x

• mws_srx644 as branch tag for 1.0.x codeline