Skip to end of metadata
Go to start of metadata

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

Update: Apache OpenOffice 4.1.11 was released on 06 October 2021. See the Release Notes for more information.

Release Schedule

The release is planned for October 2021.

Release Progress and Volunteers

Code

StartedFinishedStatusVolunteersComments
Appoint Release Manager





Edit the milestone items in Bugzilla

 

 

(tick)

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 (question):

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

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

Propose string/localization updates----Localization changes are not being considered.
Propose dictionary updates

 

 

(tick)English (en-GB) dictionary was 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----

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

 

 

(tick)

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

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)

 

 

(tick)All

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

Release

StartedFinishedStatusVolunteersComments
Go / No Go for the release (based on votes and comments)--(tick)git-hash: bdb20b2a64 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--(tick)Jim JagielskiSign macOS dmg's with Developer ID Application: The Apache Software Foundation
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.11/

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

Move builds to ASF Dist server (release area)--(tick)

-

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

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.

Create new tag

----

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


Keith McKenna
Specific QA focused on the selected bugfixes/enhancements


Keith McKenna

Communication

StartedFinishedStatusVolunteersComments

Preparation






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

-

--

Pre-Announcements are not planned

Wiki: Prepare the Release Notes

 

 

(tick)Release Notes created via template
Translation: Give participants a note so that they can create localized press release-

-

--A press release will be done for this release.
Announcement: Prepare Apache Press Release

 

 

(tick)A press release will be done for this 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.

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

Security






CVE for this release

(tick)Ask the ASF Security Team for advice or a new CVE number.

Website Updates






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.

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

 

 

(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. Especially the files "globalvars.js" and "brand.gsp" are important.

Website: Update localized AOO download pages with new version data - With customized data

 

 

(tick)

Currently the following language codes are relevant:

eu, fr, it, ja

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 on the main page to the blog post

 

 

(tick)

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

Website: Update the ASF project information

 

 (tick)

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

SourceForge: Update the "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 CVE 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.

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.

Forward the announcement to dev@

 

 

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

 

 

(tick)

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.

Announcement: CVE email

 

 

(tick)

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

 

 

(tick)

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

 

 

(tick)

Currently the following language codes are relevant:

de, nl, pl + more to come

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.11" only to the relevant products (question):

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

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.11-dev" for the relevant products (question):

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

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

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.11" as to the relevant products (question):

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

Create new tag

 

 

(tick)

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)

Update the scripting for download counting

 

 

(tick)Matthias Seidel 

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
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 but that must not happen before the Microsoft Store is updated (see below).

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

Update submission for Microsoft Store

 

 

(tick)Matthias Seidel

Microsoft Store on Windows 10 and 11:

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

Update data for OpenOffice in ReactOS (rapps-db)

 

 

(tick)See:
https://github.com/reactos/rapps-db/blob/master/openoffice.txt

Stay Informed

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

Vote Resolution

See Discussion

WhoPassedBindingWindows
Linux
macOS
Language AttentionSpecials



BinarySourceBinarySourceBinarySource

Matthiasxxxxx
x
de, en-US, pl

Windows 10 64-bit, Windows 7 32-bit,

Ubuntu 16.04 64-bit, Ubuntu 18.04 64-bit,

macOS Catalina, macOS Big Sur (M1)

Pedroxxx
xx

en-US, pt
  • Test build from source: Ubuntu 18.04 64-bit
  • Tested binary: Ubuntu 16.04 32-bit, Ubuntu 18.04 64-bit, Windows 7 Pro 64-bit, Windows 10 Pro 64-bit
  • Tested SHA512 and GPG signature of source archive tar.gz
  • Tested SHA256 and SHA512 for the Windows and Linux DEB binaries
  • Opened documents (ODT, ODS, ODP, ODF, DOC, XLS, PPT and DOCX, XLSX, PPTX)
  • Signed ODT documents with PGP and EU ID Card
Czesławx
x




en-US, de, fr, pl

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

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

Marcusxxx




en-US, de, pt

Tested checksums for all source tarballs

Tested checksums for the install files en-US, de, pt

Existing, older DOC, XLS, PPT documents

Existing, older DOCX, XLSX, PPTX documents

Created a new text doc and opened / edited the saved file with all languages

Carlxx

xx


Tested the usual file open, edit, save

Tested the Hyperlink test documents, as well as other security related test documents fixed in this RC.

Ran multiple passes of the BVT and FVT test suites on CentOS 7 and Windows 10 and except for some flaky and broken tests that still need fixed it looks good.

Verified sha256 and sha512 checksums, and signatures for tar.gz sources and rpm_en-US.tar.gz, en-US.exe, office and SDK binaries.

Extracted the source and verified the LICENSE and NOTICE files were present

Andreaxx

xx


Checked the source package contents
Found some extra files in the tree, but harmless
Found Error 500 for SourceForge downloads, fixed by adding the following line to main/solenv/bin/download_external_dependencies.pl:541 and main/solenv/bin/modules/ExtensionsLst.pm:483
      $agent->ssl_opts(verify_hostname => 0);
Tested the resulting RPMs (it) on Linux 64 opening/saving a few test documents
Jimxx

xxxx

Summary7 / 7
6 / 7
415421

  • No labels