Page History

BZ Administration - Products and the column "Open For New Issues" and "Yes". Add the new milestone item "4.1.11-dev" only for the relevant products :

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

Only for products with "Yes" in the column "Open For New Issues" and with version items from previous releases.

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)

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: bdb20b2a64) was accepted (see the vote resolution below this table).

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

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

IMPORTANT

Do not yet move the release to the public server as others are looking at it and offer it much too early. This must not happen. The files will be moved later on (see further below).

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

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 are not planned

Release Notes will be translated on demand.

No Pre-Announcements were made.

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

Website: Update the main AOO download page with new version data - With centralized data

Currently the following language codes are relevant:

eu, fr, it, ja

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

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.
https://projects.apache.org/create.html and ASF project information 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.

Don't forget a link to the source as that is the official release.

Important

Make sure to send with your Apache mail address and that the email is plain text only or it fails to get to moderation silently.

Take the text from the AOO announcement mail.

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

Important

Make sure the link to the source uses the Apache mirror system like:

https://www.apache.org/dyn/closer.lua/openoffice/4.1.11/source/

Make sure to send with your Apache mail address.

Website: Link top bar hint on the main page to the blog post

Website: Update the localized download pages with links to translated Release Notes

Currently the following language codes could be relevant:

af, am, ar, ast, bg, ca, c, da, de, el, eo, es, et, eu, fi, fr, gd, gl, he, hi, hu, hy, is, it, ja, kab, km, ko, lt, nl, no, om, pl, pt, pt-br, ro, ru, sk, sl, sr, sr-cyrl, sr-latn, sv, ta, th, tr, uk, vi, xx, zh, zh-cn, zh-tw

Website: Link top bar hint on the localized pages to the localized release notes

Currently the following language codes are relevant:

de, nl, pl + more to come

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

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

Only for products with "Yes" in the column "Open For New Issues" and with version items from previous releases.

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

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

Only for products with "Yes" in the column "Open For New Issues" and with version items from previous releases.

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

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

Only for products with "Yes" in the column "Open For New Issues" and with version items from previous releases.

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: (AOO4111-GA)

Add the new release to the scripting files that count the download numbers:

• Add all download links to the end of all.lst
• Create a new single file for the release (e.g., 41x.lst)
• Add the release number to 2 locations in detail-by-day.py

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

The older version can be removed some time after the release but that must not happen before the Microsoft Store is updated (see below).

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 some days after the release. Start with older releases earlier and finish with newer releases later.

Microsoft Store on Windows 10 and 11:

ms-windows-store://pdp/?productid=XP89J5462CMGJD