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

Update: Apache OpenOffice 4.1.9 was released on 07 February 2021. See the Release Notes for more information.

Release Schedule

The release is planned for February 2021.

Release Progress and Volunteers

Code

StartedFinishedStatusVolunteersComments
Appoint Release Manager

 

 

(tick)Jim JagielskiJim volunteers
Edit the milestone items in Bugzilla

-

 

(tick)

Add a new version item as to the relevant products:

Propose string/localization updates-

 

(tick)-Localization changes are not being considered.
Propose dictionary updates

-

 

(tick)Danish and English dictionaries were updated.
Select bugfixes and enhancements

 

 

(tick)All
Decide on the proposed release blocker

 

 

(tick)

All


Provide code for the selected bugfixes/enhancements

 

 

(tick)AllIssue List

Build

StartedFinishedStatusVolunteersComments
Buildbots--(tick)-

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

Windows 32-bit builds

 

 

(tick)

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

macOS 64-bit builds

2021.01.09

  

2021.01.11

  

(tick)

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

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

Linux 32-bit and 64-bit builds

 

 

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

 

 

(tick)Three formats: zip, gz, bz2
Upload builds to ASF Dist server (dev area)

 

 

(tick)

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.

Vote on Release Candidate(s)

 

 

 

tbd

(tick)

All

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)

Release

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

tbd

 

tbd

(tick)git-hash: 561082130a will be released.
Windows Code Signing

 

 

(tick)

Matthias SeidelSign the Windows binaries and re-upload them to dev area with new hashes and signatures.
macOS Image Signing

 

tbd

 

tbd

(tick)Jim JagielskiSign macOS dmg's with Developer ID Application: The Apache Software Foundation
Move builds to ASF Dist server (release area)

 

 

(tick)

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

Make sure builds are on the ASF Archive server

 

 

(tick)Matthias Seidel

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

Upload builds to SourceForge mirrors

 

 

(tick)

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

-

-

(tick)

-

IMPORTANT

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

QA

StartedFinishedStatusVolunteersComments
Generic QA

 

 

(tick)

Keith McKenna
Specific QA focused on the selected bugfixes/enhancements

 

 

(tick)Keith McKenna

Communication

StartedFinishedStatusVolunteersComments

Preparation






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

 

 

(tick)

Pre-Announcements planned

Draft

Final

Wiki: Prepare the Release Notes

 


 

(tick)

Release Notes created via 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: tbd

No Pre-Announcements were made.

Website: Update the main AOO test download page

-

-

(tick)-No test links were made. Tests were done only locally.

Security






CVEs for this release

-

-

(tick)

Updates






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

 

  

(tick)

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

 

 

(tick)

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

 

 

(tick)

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

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

 

 

(tick)

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)

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

SourceForge: Update to "Latest Version"

 

 

(tick)Set the attribute "Latest Version" to all full installation files for Windows, macOS and Linux (see the icons for the correct checkbox).
Mitre: Publish CVE

-

-

(tick)Publish CVE with Mitre
Website: Update security bulletins

-

-

(tick)

Adding CVEs to https://www.openoffice.org/security/bulletin.html

Mails and blog






Blog post: Write the announcement to the AOO blog

 

 

(tick)

Make sure to also include a link to the download page for the source files. For this use the download webpage of the project site.
Announcement: Write official announcement for announce@apache.openoffice.org

 

 

(tick)

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.

Forward the announcement to dev@

 

 

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

 

 

Moderator is not accepting the mail. This time without announcement.

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.

Announcement: CVE email

-

-

(tick)

Go-Live

StartedFinishedStatusVolunteersComments
The release is live

 

 

(tick)

All Many thanks to everyone involved!

Tasks after Go-Live






Edit the version items in Bugzilla

  

 

(tick)

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:

Edit the milestone items in Bugzilla

 

 

(tick)

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 ""
Edit the last confirmation items in Bugzilla

 

(tick)

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:

Create new tag

 

 

(tick)

Jim Jagielski

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)

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

 

 

(tick)

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

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

Update Feed: New check.Update for the aoo418 area and all older releases

 

 

(tick)

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.

Stay Informed

The best channels for accurate information about the release progress are:

Vote Resolution

See Discussion

WhoPassedBindingWindows
Linux
macOS
Language AttentionSpecials



BinarySourceBinarySourceBinarySource

XX

XXXX


Don Lewis

X







FreeBSD (Source and Binary)
XXXXX


de (full) + en-US (langpack)Windows 7  + 10, Ubuntu 16.04
XXX





Windows 10
X


XX


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




  • en-US (full) + de, fr, pl, pt, ru (langpack)
  • pl (full) + en-US (langpack)
Windows 7 Home 64-bit, Windows 10 Home 64-bit
XXX
X


en-US (full) + de (langpack)Windows 10 Home 64-bit, Fedora Linux 21 x86-64
XXX
XX


  • 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)
Pedro LinoX
X
XX


  • 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
Andrea PescettiXX

X


it + en-US
  • CentOS 7 x86-64, Ubuntu 20.04
  • Checked source code files
Summary10 / 106 / 10617411

Vote #2 only for the macOS install files

WhoPassedBindingWindows
Linux
macOS
Language AttentionSpecials



BinarySourceBinarySourceBinarySource












Summary? / ?? / ?



??

  • No labels