...
Code | Started | Finished | Status | Volunteers | Comments |
|---|---|---|---|---|---|
| Appoint Release Manager | |||||
| 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.14-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 | Matthias Seidel | English (en-GB) and Scottish Gaelic (gd) dictionaries were updated. | |||
| Select bugfixes and enhancements | |||||
| Decide on the proposed release blocker | |||||
| Provide code for the selected bugfixes/enhancements | |||||
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 | 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 (git-hash: tbd 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: tbd will be released. | ||||
| Windows Code Signing | Sign the Windows binaries and re-upload them to dev area with new hashes and signatures. | ||||
| macOS Image Signing | 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) | 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 | The new release is synced to archive by a cron job. That may take a while. | ||||
| Create new tag | IMPORTANT Do not create any tag until 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. | ||||
www.openoffice.org 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. | ||||
www.openoffice.org Prepare security bulletins | Adding CVE to https://www.openoffice.org/security/bulletin.html | ||||
Website Updates | |||||
Build files 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. | ||||
www.openoffice.org 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. | ||||
www.openoffice.org Website: Update localized AOO download pages with new version data - With customized data | Currently the following language codes are relevant: no separate work is needed | ||||
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). | ||||
openoffice.apache.org | This is the https://openoffice.apache.org/ website. Test again that the links are working and the metadata is correct. | ||||
openoffice.apache.org Website: Update the ASF project information | The DOAP RDF data needs to be updated. Check here if it was successful: https://projects.apache.org/project.html?openoffice | ||||
Mitre Publish CVE | Publish CVE with Mitre | ||||
www.openoffice.org Publish 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@openoffice.apache.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@ | |||||
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. If the blog was used as the announcement in the announce@openoffice.apache.org email then this one is the same. 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.14/source/ 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. | ||||
www.openoffice.org 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. | ||||
www.openoffice.org 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, cs, 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 | ||||
www.openoffice.org Website: Update the localized download pages with links to translated Release Notes | Currently the following language codes are relevant: tbd | ||||
Go-Live | Started | Finished | Status | Volunteers | Comments |
| The release is live | Many thanks to everyone involved! | ||||
Tasks after Go-Live | |||||
Bugzilla Edit the version items | BZ Administration - Products and the column "Open For New Issues" and "Yes". Add a new version item "4.1.14" only to the relevant products
| ||||
Bugzilla Edit the milestone items | BZ Administration - Products and the column "Open For New Issues" and "Yes". Disable the milestone item "4.1.14-dev" for the relevant products
| ||||
Bugzilla Edit the last confirmation items | BZ Administration - Field Values. Add a new version item "4.1.14" as to the relevant field:
| ||||
Git 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 showstopper will be found. This must be avoided in any case. New tag: (AOO4115-GA) | ||||
Git Update Readme.md | Readme.md for branch AOO41X. | ||||
www.openoffice.org 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 aoo4114 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. | ||||
Microsoft Store Update submission | "Microsoft Store" App on Windows 10 and 11. | ||||
Build files Remove "old" build from ASF Dist server (release area) | Only the most recent version should be available in the release area. Note: | ||||
Anti-Virus Send information / Update about binary files to anti-virus software vendors | In order to prevent that the new binaries get black listed and produce false-positive virus warnings, the information about the new binaries have to be send to the vendors of anti-virus software: | ||||
ReactOS Update data (rapps-db) | https://github.com/reactos/rapps-db/blob/master/openoffice.txt | ||||
Wikidata Check for updated data (Q2858086) | |||||
www.openoffice.org Update the announcement and news section | Add new items for the announcement (a short and a long entry) in the https://www.openoffice.org/index.html file |
:...