THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Apache OpenOffice 4.1.10 (AOO 4.1.10) is the next planned release of Apache OpenOffice.
Update: Apache OpenOffice 4.1.10 was released on 04 May 2021. See the Release Notes for more information.
Release Schedule
The release is planned for May 2021.
Release Progress and Volunteers
Code | Started | Finished | Status | Volunteers | Comments |
|---|---|---|---|---|---|
| Appoint Release Manager |
|
|  | Jim Jagielski | Jim volunteers |
| 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.10-dev" only for the relevant products
| |
| Propose string/localization updates | - | - | | - | Localization changes are not being considered. |
| Propose dictionary updates |
|
| | Danish, English (en-GB, en-ZA) dictionaries were updated. | |
| Select bugfixes and enhancements | | All | |||
| Decide on the proposed release blocker | | All | |||
| Provide code for the selected bugfixes/enhancements | | All | Issue List | ||
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 |
|
| | 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 | RC2 (git-hash: b1cdbd2c1b) 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) |
|
| | git-hash: b1cdbd2c1b 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 |
|
| | 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) |
|
| | 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 |
|
| | 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 | | Keith McKenna | |||
| Specific QA focused on the selected bugfixes/enhancements | | Keith McKenna | |||
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 | - | - | | - | A press release will be done for this release. |
| Announcement: Prepare Apache Press Release |
|
| | 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 |
|
| | Ask the ASF Security Team for advise or a new number | |
Website Updates | |||||
Website: Update the main AOO download page with new version 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. | |
| Website: Update the localized download pages with links to translated Release Notes |
|
| | 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 | |
| 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: Link top bar hint to the blog post |
|
| | Here the large blue headline with "Apache OpenOffice X.Y.Z released" is meant. | |
Website: Update the ASF project information |
|
| | The DOAP RDF data needs to be updated. | |
| 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). | |
| 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 |
|
| | 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 ant that the email is plain text only or it fails to get to moderation silently. | |
| Forward the announcement to dev@ |
|
| | ||
| 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. Then the ASF press team will moderate the mail. Important Make sure to send with your Apache mail address. | |
| Announcement: CVE email |
|
| | ||
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.10" 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.10-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.10" 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: (AOO4110-GA) |
| Remove "old" build from ASF Dist server (release area) | | 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 aoo419 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 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:
- 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 | |||||
| Jim | x | x | x | x | x | x | ||||
| Matthias | x | x | x | x | x |
|
| |||
| Keith | x | x | x |
| ||||||
| Carl | x | x | x | x |
| |||||
| Don | x |
| ||||||||
| Czesław | x | x |
|
| ||||||
| Arrigo | x | x | x |
| ||||||
| Kazunari | x | x | x | |||||||
| Marcus | x | x | x |
|
| |||||
| Pedro | x | x | x | x | x |
| ||||
| Summary | 10 / 10 | 7 / 10 | 7 | 1 | 4 | 4 | 1 | 1 | ||