Release Planning Template

• Start

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

• 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

• End

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

• Start

• • Update RN with new languages

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

• Start

• End

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

• Start

• • Start release blocker mode

• • Update all bundled dictionaries

• • Update RN with latest changes

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

• Start

NL community

• End

• 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
  • Update devbuilds.html

• 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
  • 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

• 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 BZ
  • Add/modify values for:
  • "Version", "Target milestone", "Release blocker flag"

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

• Update "w.oo.o" homepage
  • Create new blog and/or news entry
  • Update headline below the logo

• Create a "kid" build for translation testing

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

• Update "globalvars.js" file with:
  • 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
    • Insert the data in the correct order for the new
      languages.

SEL_LANG

• • Enable the Beta Release.

• Update "release_matrix.js" file with:
  • Add a new array for the new release.
  • Is the file for the respective platform available (y/n) ?
  • Collect the file sizes for every file.

release_xyz

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

Also look at the comments on top of the file.

• Update "download.js" file with:
  • Insert a new "case" section for the new version in all "switch()" statements of the following functions:
    • isLangSupported()
    • getFileData()

case "x.y.z" :

...

break;

• Update "globalvars.js" file with:
  • 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
    • Verify that the data is complete and in the correct order for the new languages.

SEL_LANG

• • Disable the Beta Release.

• Update "release_matrix.js" file with:
  • 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.

• Update "download.js" file with:
  • Verify that all "case" sections have correct data for the new version in all "switch()" statements in the following functions:
  • • isLangSupported()
    • getFileData()

case "x.y.z" :

...

break;