Difference between revisions of "Branch off"
(add category releases) |
|||
| Line 9: | Line 9: | ||
The date of the '''branch off''' will be announced on the wiki page for the corresponding release. E.g. the page for [http://wiki.services.openoffice.org/wiki/OOoRelease32 OOo 3.2 release]. | The date of the '''branch off''' will be announced on the wiki page for the corresponding release. E.g. the page for [http://wiki.services.openoffice.org/wiki/OOoRelease32 OOo 3.2 release]. | ||
| − | + | [[Category:Releases]] | |
Revision as of 14:37, 23 October 2009
Meaning
The term branch off or branch off date is used by release engineers and release managers of OOo. With this term they want to identify the date when the release code-line is split from the general developer code line (see the picture). Until the branch off features, enhancements and general integrations can be done on the development code line. But it is important to be finalize all implementations until this date. This means features, enhancements and general integrations must be completed. On the release code-line only stopper issues are excepted. This should stabilize until builds/milestones until the release. General development can be done on the development code-line (DEV300).
When is the branch off?
The date of the branch off will be announced on the wiki page for the corresponding release. E.g. the page for OOo 3.2 release.
