...
The release is planned for <month> 2020. See the Release Notes for more information.
Release Progress and Volunteers
Code | Started | Finished | Status | Volunteers | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Appoint Release Manager |  | ||||||||||
| Propose string/localization updates | - | - |  | - | Localization changes are not being considered. | ||||||
| Propose dictionary updates | - | - | Danish, English and Lithuanian 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.12 (Sierra w/ Xcode7) | |||||||||
| Linux 32-bit and 64-bit builds | | 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) | | RC<x> (git-hash: xxxxxxxx) 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) | Release Manager | Which revision will be released.? | |||||||||
| Windows Code Signing | Matthias Seidel | Sign the Windows binaries and re-upload them to dev-area with new hashes and signatures. | |||||||||
| Move builds to ASF Dist server (release area) | Release Manager | 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 | Release Manager | Hash files must not be stored on public servers but only on ASF servers. | |||||||||
| Upload builds to SourceForge mirrors | Release Manager | 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. | |||||||||
Create new tag | Release Manager | 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 | 2020-06-15 | Keith McKenna | |||||||||
| Specific QA focused on the selected bugfixes/enhancements | 2020-06-15 | Keith McKenna | |||||||||
Communication | Started | Finished | Status | Volunteers | Comments | ||||||
Preparation | |||||||||||
| Blog post: First status update and call for volunteers on dev@ mailing list | - | - | | - | No Pre-Announcements were made. | ||||||
| Wiki: Prepare the Release Notes | 2020-07-07 |
| Release Notes created via template | ||||||||
| Translation: Give participants a note so that they can create localized press release | - | - | | - | No press release was done. | ||||||
| Announcement: Prepare Apache Press Release | - | - | | - | No press release was done. | ||||||
| Translation: Give participants a note so that they can create localized release notes | | Release Notes are translated to: tbd | |||||||||
| Website: Update the main AOO test download page | - | - | | - | No test links were made. Tests were done only locally. | ||||||
Updates | |||||||||||
| Website: Update the main AOO download page | 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. | xx and de were already done, just need to be published. 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 | 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 to "Latest Version" | Set the attribute "Latest Version" to all full installation files for Windows, macOS and Linux (see the icons for the correct checkbox). | ||||||||||
Mails and blog | |||||||||||
| Blog post: Write the announcement to the AOO blog |
| ||||||||||
| Announcement: Write official announcement for announce@apache.openoffice.org |
| ||||||||||
| Announcement: Copy the official announcement for announce@apache.org | | 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. | |||||||||
| Forward the announcement to dev@ | | ||||||||||
Go-Live | Started | Finished | Status | Volunteers | Comments | ||||||
| The release is live | All | ||||||||||
Tasks after Go-Live | |||||||||||
Create new tag | | 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. | |||||||||
| Update Feed: New check.Update for the aoo417 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. |
...