BZ Administration—Products and the column "Open For New Issues" and "Yes". Add the new milestone item "4.1.14-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.

Issue List
Commit List

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: a0d24fb625) 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.14/

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).

The new release is synced to archive by a cron job. That may take a while.

IMPORTANT

Do not create any tag until the release is actually done and published (see "Tasks after Go-Live").

Blog post

First status update and call for volunteers on dev@ mailing list

Pre-Announcements are not planned

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

Release Notes will be translated on demand.

No Pre-Announcements were made.

www.openoffice.org

Update the main AOO test download page

Build files

Move builds to ASF Dist server (release area)

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

www.openoffice.org

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

Currently the following language codes are relevant:

no separate work is needed

SourceForge

Update the "Latest Version"

openoffice.apache.org

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

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

openoffice.apache.org

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.

Check here if it was successful: https://projects.apache.org/project.html?openoffice

Mitre

Publish CVE

www.openoffice.org

Update security bulletins

Blog post

Write the announcement to the AOO blog

Mail

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

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.

Mail

Forward the announcement to dev@

Mail

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

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. 

If the blog was used as the announcement in the announce@openoffice.apache.org email then this one is the same.

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.14/source/

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.

www.openoffice.org

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

Here the large blue headline with "Released: Apache OpenOffice X.Y.Z" is meant.

www.openoffice.org

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

Here the large blue headline with "Released: Apache OpenOffice X.Y.Z" is meant.

Currently the following language codes could be relevant:

af, am, ar, ast, bg, ca, cs, 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

www.openoffice.org

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

Currently the following language codes are relevant:

pl, nl, fr

Bugzilla

Edit the version items

BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.14" 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.

Bugzilla

Edit the milestone items

BZ Administration - Products and the column "Open For New Issues" and "Yes". Disable the milestone item "4.1.14-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.

Bugzilla

Edit the last confirmation items

BZ Administration - Field Values. Add a new version item "4.1.14" as to the relevant field:

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

Git

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 showstopper will be found. This must be avoided in any case.

New tag: (AOO4114-GA)

www.openoffice.org

Update the scripting for download counting

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

Update Feed

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

Microsoft Store

Update submission

"Microsoft Store" App on Windows 10 and 11.
https://apps.microsoft.com/store/detail/apache-openoffice/XP89J5462CMGJD

Build files

Remove "old" build from ASF Dist server (release area)

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

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

ReactOS

Update data (rapps-db)

Wikidata

Check for updated data (Q2858086)

https://www.wikidata.org/wiki/Q2858086 (apparently data was automatically updated)

www.openoffice.org

Update the announcement and news section

Add new items for the announcement (a short and a long entry) in the https://www.openoffice.org/index.html file