Add a new version item as to the relevant products:

• On the "Milestone" webpage add a new item (see on the bottom)

• https://bz.apache.org/ooo/show_bug.cgi?id=128415
• https://github.com/apache/openoffice/commit/1d5f25b3a6d735ba43bcd728fa141b3a24bbcb5d
• https://bz.apache.org/ooo/show_bug.cgi?id=128413

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

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

Build server: macOS 10.13 (High Sierra w/ Xcode10)

Due to a build error new install files only for macOS are needed

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.

RC1 (git-hash: 561082130a) was accepted (see the vote resolution below this table).

A new vote only for the macOS install files are needed (see the 2nd vote resolution below this table)

According to the Infrastructure team they do not need to know about a new release. There is no special preparation needed anymore.

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

Make sure it is 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 now but when the release is actually done and published (see "Tasks after Go-Live").

Pre-Announcements planned

Draft

Final

27 Dec 2020 

-

Release Notes are translated to: tbd

No Pre-Announcements were made.

-

Website: Update the main AOO download page

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, ta, th, tr, vi, xx, zh-CN, zh-TW

Locally prepared:
ast, bg, ca, cs, da, de, el, es, eu, fi, fr, gd, gl, he, hi, hu, it, ja, lt

Locally prepared:
kab, km, ko, nl, no, om, pl, pt, pt-BR, ru, sk, sl, sr, sv, ta, th, tr, uk, 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.

The DOAP RDF data needs to be updated.
https://projects.apache.org/create.html can be helpful.

Don't forget to create the 3 short URLs for Blog announcement, Release Notes and BZ changes list. Use the Apache URL Shortener. These are used in both mail announcements.

Make sure to send with your Apache mail address.

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.

Make sure to send with your Apache mail address.

BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.9" only to the relevant products:

• On the "Version" webpage add a new item (see link on the bottom)

BZ Administration - Products and the column "Open For New Issues" and "Yes". Disable the milestone item "4.1.9-dev" for the relevant products:

• On the "Milestone" webpage click on the version item and uncheck the option "Enabled For Issues"

BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.9" as to the relevant products:

• On the "Latest Confirmation" webpage add a new item (see link on the bottom)

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.

New tag: (AOO419-GA)

Only the most recent version should be available in the release area.

The older version can be removed some time after the release.

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.

Don Lewis

• Ubuntu 18.04, CentOS 5 x86-64 + x86, openSUSE Leap 15.2
• Checked source code files

• en-US (full) + de, fr, pl, pt, ru (langpack)
• pl (full) + en-US (langpack)

• CentOS 7 x86-64, CentOS 8 Stream, x86-64, Ubuntu 18.04 x86-64 Windows 10 64-bit
• Checked source code files and SDK
• Ran the BVT and FVT automated test suites
• basic document tests (saving, editing, re-saving)

• Ubuntu 18.04 x86-64, Ubuntu 14.04 x86, Ubuntu 20.04 x86-64, Windows XP 32-bit, Windows 7 64-bit
• Checked SHA256 and SHA512 for the Windows and Linux DEB binaries
• Tested with ODT, ODS, ODP, ODF, DOC, XLS, PPT, DOCX, XLSX, PPTX documents
• Checked for Updates and Extension Updates

• CentOS 7 x86-64, Ubuntu 20.04
• Checked source code files