Apache OpenOffice 4.1.7 (AOO 4.1.7) is the next planned release of Apache OpenOffice.

Update: Apache OpenOffice 4.1.7 was released on 21 September 2019. See the Release Notes for more information.

Release Schedule

The release is planned for September 2019.

Release Progress and Volunteers


Appoint Release Manager



Propose string/localization updates--(tick)-Language changes are not being considered. They will be prepared for 4.2.x
Propose dictionary updates--(tick)English and Asturian dictionaries were updated
Select bugfixes and enhancements--(tick)All

Decide on the proposed release blocker--(tick)


Provide code for the selected bugfixes/enhancements



(tick)AllIssue List



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



(tick)Matthias Seidel

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

macOS 64-bit builds

(tick)Jim JagielskiBuild server: macOS 10.13 (High Sierra w/ Xcode10 and SDX 10.11)
Linux 32-bit and 64-bit builds



(tick)Jim JagielskiCentOS 5, both rpm and deb
Source builds



(tick)Jim JagielskiThree 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 Release Distribution Policy.

Vote on Release Candidate(s)



(tick)RC1 (git-hash: 46059c9192) was accepted. See the vote resolution below.


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



(tick)Jim Jagielski

git-hash: 46059c9192 will be released.

Move builds to ASF Dist server (release area)



(tick)Jim Jagielski

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



(tick)Jim Jagielski

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

Upload builds to SourceForge mirrors



(tick)Jim Jagielski

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



(tick)Jim Jagielski


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.


Generic QA



Specific QA focused on the selected bugfixes/enhancements





Blog post: First status update and call for volunteers on dev@ mailing list--(tick)-No Pre-Announcements were made.
Wiki: Prepare the Release Notes



(tick)Base Note created from template.
Translation: Give participants a note so that they can create localized press release--(tick)
No press release was done
Announcement: Prepare Apache Press Release--(tick)
No press release was done
Translation: Give participants a note so that they can create localized release notes--(tick)

Release Notes are translated to: Dutch, French

Website: Update the main AOO test download page--(tick)

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



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





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


(tick)Matthias Seidel

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



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



(tick)Marcus LangeThe DOAP RDF data needs to be updated.
Remove "staged" flag from the new release directory at SourceForge




SourceForge: Update to "Latest Version"



(tick)Marcus LangeSet 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



(tick)Marcus Lange
Announcement: Write official announcement for announce@apache.openoffice.org



(tick)Marcus Lange
Announcement: Copy the official announcement for announce@apache.org



(tick)Marcus Lange


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@



(tick)Marcus Lange
Update Feed: New check.Update for the aoo416 area and all older releases


(tick)Matthias Seidel

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



(tick)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





USTested binaries on Windows 10


German fullWin 7, Win 10, Ubuntu 32-bit, Ubuntu 64-bit, Xubuntu 32-bit

US full, German langpackWin 10, Fedora 64-bit

Built from source on FreeBSD

  • No labels