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

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

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 Release Distribution Policy.

git-hash: 46059c9192 will be released.

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.

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

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.1.7/.

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

Create new tag

Important

Do not create any 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.

Release Notes are translated to: Dutch, French

All

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

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

Important

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.

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.