Apache OpenOffice 4.1.12 (AOO 4.1.12) is the next planned release of Apache OpenOffice.
Update: Apache OpenOffice 4.1.12 was released on 04 May 2022. See the Release Notes for more information.
Release Schedule
The release is planned for May 2022.
Release Progress and Volunteers
Code | Started | Finished | Status | Volunteers | Comments |
|---|---|---|---|---|---|
| Appoint Release Manager |  | Jim was the only volunteer. | |||
| Edit the milestone items in Bugzilla |
|
| | BZ Administration - Products and the column "Open For New Issues" and "Yes". Add the new milestone item "4.1.12-dev" only for the relevant products
| |
| Propose string/localization updates | - | - | - | - | Localization changes are not being considered. Specific strings were patched in SDF files. |
| Propose dictionary updates | | English (en-GB) dictionary was updated. | |||
| Select bugfixes and enhancements | - | - | | All | |
| Decide on the proposed release blocker | - | - | | All | |
| Provide code for the selected bugfixes/enhancements | - | - | | All | |
Build | Started | Finished | Status | Volunteers | Comments |
| 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 | | Build platform: Windows 10 (64-bit) because we provide Windows 64-bit shell extensions. | |||
| macOS 64-bit builds |
|
| | Jim Jagielski | Build server: macOS 10.13 (High Sierra w/ Xcode10) |
| Linux 32-bit and 64-bit builds |
|
| | Jim Jagielski | CentOS 5, both rpm and deb |
| Source builds |
|
| | Three 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 updated Release Distribution Policy. | |
| Vote on Release Candidate(s) |
|
| | All | RC1 (git-hash: 60e0a1c111) was accepted (see the vote resolution below this table). |
Release | Started | Finished | Status | Volunteers | Comments |
| Go / No Go for the release (based on votes and comments) | - | - | | Jim Jagielski | git-hash: 60e0a1c111 will be released. |
| Windows Code Signing | | Matthias Seidel | Sign the Windows binaries and re-upload them to dev area with new hashes and signatures. | ||
| macOS Image Signing |
|
| | Jim Jagielski | Sign macOS dmg's with Developer ID Application: The Apache Software Foundation |
| Upload builds to SourceForge mirrors | | 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 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) | - | - | | - | 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 | | 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 | Started | Finished | Status | Volunteers | Comments |
| Generic QA | | ||||
| Specific QA focused on the selected bugfixes/enhancements | - | - | - | - | |
Communication | Started | Finished | Status | Volunteers | Comments |
Preparation | |||||
| Blog post: First status update and call for volunteers on dev@ mailing list | - | - | - | - | Pre-Announcements are not planned |
| Wiki: Prepare the Release Notes |
|
| | Release Notes created via template | |
| Translation: Give participants a note so that they can create localized press release | - | - | - | - | No press release will be done for this release. |
| Announcement: Prepare Apache Press Release | - | - | - | - | No 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 | Ask the ASF Security Team for advice or a new CVE number. | ||||
Website Updates | |||||
| Move builds to ASF Dist server (release area) | | Jim Jagielski | 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 |
|
| | 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 |
|
| | Currently the following language codes are relevant: ja | |
| SourceForge: Update the "Latest Version" |
|
| | Set the attribute "Latest Version" to all full installation files for Windows, macOS and Linux (see the icons for the correct checkbox). | |
| 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. | ||
Website: Update the ASF project information | | The DOAP RDF data needs to be updated. | |||
| Mitre: Publish CVE | Publish CVE with Mitre | ||||
| Website: Update security bulletins | Adding CVE to https://www.openoffice.org/security/bulletin.html | ||||
Mails and blog | |||||
| Blog post: Write the announcement to the AOO blog |
|
| | Carl B. Marcum | 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 |
|
| | 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@ |
|
| | Carl B. Marcum | |
| Announcement: Copy the official announcement for announce@apache.org |
|
|
| Carl B. Marcum | 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.12/source/ Make sure to send with your Apache mail address. |
| 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, 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: Update the localized download pages with links to translated Release Notes |
|
| | Currently the following language codes could be relevant: nl + maybe more | |
Website: Link top bar hint on the localized pages to the localized release notes |
|
|
| Currently the following language codes are relevant: tbd | |
| 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. | |
Go-Live | Started | Finished | Status | Volunteers | Comments |
| The release is live |
| | All | Many thanks to everyone involved! | |
Tasks after Go-Live | |||||
| Edit the version items in Bugzilla |
|
|
| BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.12" only to the relevant products
| |
| Edit the milestone items in Bugzilla |
|
| | BZ Administration - Products and the column "Open For New Issues" and "Yes". Disable the milestone item "4.1.12-dev" for the relevant products
| |
| Edit the last confirmation items in Bugzilla |
|
| | BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.12" as to the relevant products
| |
Create new tag |
|
| | 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: (AOO4112-GA) |
| Update the scripting for download counting | | Add the new release to the scripting files that count the download numbers:
| |||
| Update Feed: New check.Update for the aoo4111 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. | |||
| Update submission for Microsoft Store | | Matthias Seidel | "Microsoft Store" App on Windows 10/11: https://apps.microsoft.com/store/detail/apache-openoffice/XP89J5462CMGJD | ||
| Remove "old" build from ASF Dist server (release area) |
|
| | Jim Jagielski | Only the most recent version should be available in the release area. Note: |
| Update data for OpenOffice in ReactOS (rapps-db) | | See: https://github.com/reactos/rapps-db/blob/master/openoffice.txt |
:
Stay Informed
The best channels for accurate information about the release progress are:
- The development mailing list archives
- The Apache OpenOffice official blog
- The Git branch where the development is actually done
Vote Resolution
See Discussion
| Who | Passed | Binding | Windows | Linux | macOS | Language Attention | Specials | |||
| Binary | Source | Binary | Source | Binary | Source | |||||
| Matthias | x | x | x | x | x | x | de, en-US, pl | Windows 11 64-bit, Windows 7 32-bit, Ubuntu 16.04 64-bit, Ubuntu 18.04 64-bit, macOS Catalina, macOS Monterey (M1) | ||
| Jim | x | x | x | x | x | x | en-US, es | |||
| Marcus | x | x | x | en-US, de, es | Tested checksums for all source tarballs Tested checksums for the install files en-US, de, es Existing, older DOC, XLS, PPT documents Existing, older DOCX, XLSX, PPTX documents Created new docs for Writer, Calc, Impress and opened / edited the saved file with all languages | |||||
| Arrigo | x | x | x | x | Source: Linux x86, Linux x86_64 Binaries: Linux x86_64 | |||||
| Pedro | x | x | x | x | x | Checked the Source signature and SHA256 and SHA512 CRCs as well as both CRCs for the Linux x64 and Windows x86 main installer in en-US and PT and for the PT language pack binaries Installed the en-US plus PT language packs as well as the PT installer under Windows 7 x64, and Linux Ubuntu 20.04 x64. On Linux Ubuntu 20.04 x64 opened ODT, ODS, ODP and ODF as well as DOC, XLS, PPT and DOCX, XLSX and PPTX files without any issues. | ||||
| Carl | x | x | x | x | x | Used the en-US rpm install for Linux and the en-US exe for Windows and also installed the SDK for both platforms. Verified checksums and signatures for these binaries and source tarballs. Besides the usual testing of existing documents and creating new documents, ran through an automated test. | ||||
| Don | x | Built and tested on FreeBSD | ||||||||
| Summary | 7 / 7 | 6 / 6 | 4 | 1 | 5 | 4 | 2 | 1 | ||