View Source

The purpose of the following table is to provide a schedule plan for a new release planning.

It is desired for a new major release (x.y like 4.1) but it could be also used for a minor release (x.y.z like 4.1.1).

Important:

Please do not fill the template with data for a new release but copy & paste it and create a new page.

Phases and steps in schedule	Date	Responsible
Feature freeze
Start	?	Committer
Announce it on dev@, qa@, l10n@	?	Release Manager
Update version / milestone / build ID data in SVN e.g., "4.1.0" --> "4.2.0"	?	Developer
Create new branch in SVN for the new release	?	Developer
Create Release Notes (RN) in Confluence Wiki Use page name like "AOO+X.Y.Z+Release+Notes Example: AOO 4.0.1 Release Notes	?	Committer
String freeze
Start	?	NL community
Update RN with new languages	?	Release Manager
Announce it on dev@, qa@, l10n@	?	Release Manager
Translation phase
Changes in strings for the application UI and Help as well as for dictionaries
Start	?	NL community
End	?	NL community
Announce it on dev@, qa@, l10n@	?	Release Manager
Code freeze
Start	?	Committer
Start release blocker mode (aka show stopper mode)	?	Release Manager
Update all bundled dictionaries	?	L10N list
Update RN with latest changes	?	All people
Announce it on dev@, qa@, l10n@	?	Release Manager
Beta Release
Build the RC	?	Release Manager
Update Wiki page to make the files available Development Snapshot Build Make sure the files have the correct access permissions	?	Release Manager
Start vote	?	Release Manager
Announce vote on dev@, qa@, l10n@	?	Release Manager
Start Beta testing phase	?	QA
Update RN with latest changes	?	All people
Start translating RN	?	NL community
Announce it on dev@ (+ qa@, l10n@)	?	Release Manager
End Beta testing phase	?	QA
Announce vote results on dev@ (+ qa@, l10n@)	?	Release Manager
Upload files to Apache Dist/SourceForge Make sure to set the staging bit for the Beta directory	?	Release Manager
Update download scripting – javascript files in /download See [1] in the next table below for details	?	Committer
Remind the release blocker mode Announce it on dev@, qa@, l10n@	?	Release Manager
Release Candidate
Build the RC	?	Release Manager
Update Wiki page to make the files available Development Snapshot Builds Make sure the files have the correct access permissions Update devbuilds.html	?	Release Manager
Start vote	?	Release Manager
Announce vote on dev@, qa@, l10n@	?	Release Manager
Start RC testing phase	?	QA
Update RN with latest changes	?	All people
Update translating RN	?	NL community
Announce it on dev@ (+ qa@, l10n@)	?	Release Manager
End RC testing phase	?	QA
End vote (date and time in UTC timezone)	?	Release Manager
Announce vote results on dev@ (+ qa@, l10n@)	?	Release Manager
General Availability
Prepare
Upload files to Apache Dist/SourceForge Make sure to set the staging bit for the RC directory	?	Release Manager
Update download scripting See [2] in the next table below for details	?	Committer
Verify RN if all is correct	?	All people
Public Announcement of GA Announce it on announce@, dev@	?	Release Manager
After release job
Update BZ Add/modify values for: "Version", "Target milestone", "Release blocker flag"	?	BZ Admin
Update version / milestone / build ID data in SVN e.g., "4.1.0" --> "4.2.0"	?	Developer
Update "w.oo.o" homepage Create new blog and/or news entry Update headline below the logo	?	Committer
Create a "kid" build for translation testing	?	Release Manager
Announce it on dev@, qa@, l10n@	?	Release Manager

[1] Beta: Update download scripting (in /download web area)	Variables	Value example
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 - Update if needed Insert the data in the correct order for the new languages.	SEL_LANG	"English name", "native name", "ISO code"
Enable the Beta Release.	BETA_ACTIVE	1
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;	For an example please have a look for a previous version.
[2] Release Candidate: Update download scripting
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	"English name", "native name", "ISO code"
Disable the Beta Release.	BETA_ACTIVE	-1
Update "release_matrix.js" file with: 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.
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;	For an example please have a look for a previous version.