Release Planning Template

• Start

• Announce it on dev@, qa@, l10n@

• Update version / milestone / build ID data in SVN
  • e.g., "4.1.0" --> "4.2.0"

• Create new branch in SVN for the new release

• Create Release Notes (RN) in Confluence Wiki
  • Use page name like "AOO+X.Y.Z+Release+Notes
    Example: AOO 4.0.1 Release Notes

• Start

• • Update RN with new languages

• • Announce it on dev@, qa@, l10n@

• Changes in strings for the application UI and Help as well as for dictionaries

• Start

• End

• Announce it on dev@, qa@, l10n@

• Start

• • Start release blocker mode (aka show stopper mode)

• • Update all bundled dictionaries

• • Update RN with latest changes

• • Announce it on dev@, qa@, l10n@

• Build the RC

• Update Wiki page to make the files available
  • Development Snapshot Build
  • Make sure the files have the correct access permissions

• Start vote

• Announce vote on dev@, qa@, l10n@

• Start Beta testing phase

• Update RN with latest changes

• Start translating RN

• Announce it on dev@ (+ qa@, l10n@)

• End Beta testing phase

• Announce vote results on dev@ (+ qa@, l10n@)

• Upload files to Apache Dist/SourceForge
  • Make sure to set the staging bit for the Beta directory

• Update download scripting  – javascript  files in /download
  
  • See [1] in the next table below for details

• Remind the release blocker mode
  • Announce it on dev@, qa@, l10n@

• Build the RC

• Update Wiki page to make the files available

• • Development Snapshot Builds
  • Make sure the files have the correct access permissions
  • Update devbuilds.html

• Start vote

• Announce vote on dev@, qa@, l10n@

• Start RC testing phase

• Update RN with latest changes

• Update translating RN

• Announce it on dev@ (+ qa@, l10n@)

• End RC testing phase

• End vote (date *and* time in UTC timezone)

• Announce vote results on dev@ (+ qa@, l10n@)

• Prepare

• • Upload files to Apache Dist/SourceForge
    • Make sure to set the staging bit for the RC directory

• • Update download scripting
    • See [2] in the next table below for details

• • Verify RN if all is correct

• Public Announcement of GA
  • Announce it on announce@, dev@

• Update data in Bugzilla:
  
  • Add/modify values for:
    • "Version", "Target milestone", "Release blocker flag", "Last Confirmation on"

• Update version / milestone / build ID data in SVN:
  • e.g., "4.1.0" --> "4.2.0"

• Update "www.openoffice.org" homepage:
  • Create new blog and/or news entry
  • Update news entry on homepage
  • Update headline below the logo

• Update DOAP file:
  • https://svn.apache.org/repos/asf/openoffice/site/trunk/content/openoffice.rdf

• Create a "kid" build:
  • This helpful and often asked for translation testing.
  • Announce it on dev@, qa@, l10n@

• "globalvars.js":
  
  • Add the new version data,

BETA_VERSION
BETA_NAME
BETA_MILESTONE
BETA_BUILD
BETA_SVN_REV
BETA_REL_DATE

"X.Y.Z-Beta"
"X.Y.Z Beta"
"AOOXYZm??"
"????"
"r???????"
"YYYY-MMM-DD"

• • Language data - update if needed:
    
    • Insert the data in the correct order for the new languages.

SEL_LANG

• • Enable the Beta Release.

• "release_matrix.js":
  
  • Add a new array for the new release.
  • Add new languages Is the file for the respective platform available (y/n) ?
  • Add the file sizes for every file.
  • Verify that the data is complete and in the correct order for the new languages.

release_xyz

For an example please have a look for a previous version.

Also look at the comments on top of the file.

Add the data for new languages.

• "download.js":
  
  • Add data for the new version in the "switch()" statement in the following object methods:
    • DL.isLanguageSupported
    • DL.getFileData

case "x.y.z" :

...

break;

• "languages.js":
  
  • Move new languages to the top part of "DL.language_matrix".
  • Add new languages if not available in the bottom part. Check for ISO code, English name and native name.

• "globalvars.js":
  
  • Add the new version data.

VERSION
MILESTONE
BUILD
SVN_REV
REL_DATE
PREV_VERSION

"X.Y.Z-Beta"
"AOOXYZm??"
"????"
"r???????"
"YYYY-MMM-DD"
Use the value from the previous version.

• • Language data - update if needed:
    • Insert the data in the correct order for the new languages.

SEL_LANG

• • Disable the Beta Release.

• "release_matrix.js":
  
  • Add a new array for the new release.
  • Add new languages Is the file for the respective platform available (y/n) ?
  • Add the file sizes for every file.
  • Verify that the data is complete and in the correct order for the new languages.

For an example please have a look for a previous version.

Also look at the comments on top of the file.

Add the data for new languages.

Get the file sizes from Sourceforge.net.

• "download.js":
  
  • Add data for the new version in the "switch()" statement in the following object methods:
  • • DL.isLanguageSupported
    • DL.getFileData

case "x.y.z" :

...

break;

• "languages.js":
  
  • Move new languages to the top part of "DL.language_matrix".
  • Add new languages if not available in the bottom part. Check for ISO code, English name and native name.

'ca', 'Catalan', 'Català'
'ca-XR', 'Catalan', 'Català (Valencià RACV)'
'ca-XV', 'Catalan (Valencian)', 'Català (Valencià AVL)'

• ".../xx/download/brand.mdtext":
  
  • Modify the data to reflect the new release.

New: Apache OpenOffice 4.1.1 released!
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.1+Release+Notes
New: Apache OpenOffice 4.1.1 released!

• ".../xx/download/msg_properties_l10n_xx.js":
  
  • Add new languages and the new version.

l10n.dl_green_box_select_box_language_values
l10n.dl_green_box_select_box_version_values

Catalan
Catalan [Valencia AVL]
Catalan [Valencia RACV]

4.1.1

Add new languages with localized strings. They have to be in the same order as they would appear in the main English drop-down-box. Otherwise the wrong language is offered in the download links.

Add also new version item.

• • Add new method name and value for the link to the release notes.

l10n.dl_rel_notes_aoo<xyz>_link

Example:
l10n.dl_rel_notes_aoo411_link