Apache OpenOffice 4.2.0 (AOO 4.2.0) is a minor release with focus on bug fixes and enhancement, improvements, and features.

Detailed Release Planning

A more detailed release planning can be found under AOO 4.2.0 Release Planning

Release Notes

The related release notes can be found under AOO 4.2.0 Release Notes

Test and QA Plan

The related test and QA plan can be found under AOO 4.2.0 Testing Plan

Developer Snapshots

AOO 4.2.0 Dev 5

Release Schedule

The release is planned for TBD.

Release Progress and Volunteers


Appoint Release Manager

Propose string/localization updatesafter string freezebefore building beta version
main work is to commit all relevant *.sdf files to SVN (trunk) and merge them to AOO42
Propose dictionary updates

Select bugfixes and enhancements

Open List from Discussion

Decide on the proposed release blocker

Provide code for the selected bugfixes/enhancements




Buildbots available for Windows and Linux. macOS still missing but not a blocker (we don't need a buildbot for macOS release builds)

Windows 32-bit builds

Build platform: Windows 10 (64-bit), because we use Windows 64-bit shell extensions

macOS 64-bit builds

Build server: macOS 10.13 (Sierra w/ Xcode7)
Linux 32-bit and 64-bit builds

CentOS 7, both rpm and deb
Source builds

Three formats: zip, gz, bz2
Upload builds to ASF Dist server (dev area)

Since the dev area is an ASF controlled resource, we need to make sure we have the hashes and PGP signatures uploaded with the actual builds.

Note the updated Release Distribution Policy.

Vote on Release Candidate(s)



Go / No Go for the release (based on votes and comments)

Move builds to ASF Dist server (release area)

According to the Infrastructure team no special preparations are needed anymore.

The Infrastructure team needs to know about an upcoming release to be able to prepare servers and resources and to make sure they are up and running.

Make sure builds are on the ASF Archive server

Hash files must not be stored on public servers but only on ASF servers.

Upload builds to SourceForge mirrors

Copy requires just a few hours, with the normal rsync instructions shown; note: project name has changed since 4.1.2 and now the rsync target must be written as username@frs.sourceforge.net:/home/frs/mirror/openofficeorg/4.2.0/.

Make sure it's going into a "staged" directory to hide it from the public until the official release date.

Create new SVN tag


Do not create any SVN tag as long as the release is not officially announced and public available. Otherwise the created build files cannot be published when a late show stopper will be found. This must be avoided in any case.


Generic QA

Specific QA focused on the selected bugfixes/enhancements



Blog post: First status update and call for volunteers on dev@ mailing list--
Wiki: Prepare the Release Notes



Translation: Give participants a note so that they can create localized press release--
Announcement: Prepare Apache Press Release--
Translation: Give participants a note so that they can create localized release notes

Website: Update the main AOO test download page

No test links were made. Tests were done only locally.
Website: Update the main AOO download page

After the test was successful, do the changes in the Live-System. Test again that the links are working and the metadata is correct.
Website: Update the localized download pages.

xx and de were already done, just needed to be published.

Currently the following language codes are relevant:

ast, bg, ca, cs, da, de, el, es, eu, fi, fr, gd, gl, he, hi, hu, it, ja, km, ko, lt, nl, no, pl, pt, pt-BR, ru, sk, sl, sr, sv, th, tr, vi, xx, zh-CN, zh-TW

Website: Update the project's AOO pages: main and download

Let's consolidate changes from both persons that were done independently by accident.

This is the https://openoffice.apache.org/ website. Test again that the links are working and the metadata is correct.

Website: Link top bar hint to the blog post

Here the large blue headline with "Released: Apache OpenOffice X.Y.Z " is meant.
Website: Update the ASF project information

The DOAP RDF data needs to be updated.
Delete "staged" flag from the new release directory at SourceForge

SourceForge: Update to "Latest Version"

Set the attribute "Latest Version" to all full installation files for Windows, macOS and Linux (see the icons for the correct checkbox).
Blog post: Write the announcement to the AOO blog

Announcement: Write official announcement for announce@apache.openoffice.org

Announcement: Copy the official announcement for announce@apache.org


Make sure to exchange the announcement link to from our AOO Wiki webpage into the one from the ASF Blog webpage. To make look more ASF official. Then the ASF press team will moderate the mail.

Forward the announcement to dev@

Update Feed: New check.Update for the aoo415 area and all older releases

The update notification will create a high load on the mirror servers as a lot of users will then update their AOO installation. This must be avoided.

Therefore this task has to be done always 1-2 weeks after the release. Start with older releases earlier and finish with newer releases later.


The release is live

All Many thanks to everyone involved!

Stay Informed

The best channels for accurate information about the release progress are:

Vote Resolution

See Discussion

Language AttentionSpecials


Summaryx / yx / y

  • No labels