Apache OpenOffice 4.1.6 (AOO 4.1.6) is the next planned release of Apache OpenOffice.
Update: Apache OpenOffice 4.1.6 was released on 18 November 2018. See the Release Notes for more information.
Release Schedule
The release is planned for November 2018.
Release Progress and Volunteers
Code | Started | Finished | Status | Volunteers | Comments |
|---|---|---|---|---|---|
| Appoint Release Manager |  | He was the only volunteer | |||
| Propose string/localization updates | - | - | | - | Language changes are not being considered |
| Propose dictionary updates | | Matthias Seidel | English dictionary was updated | ||
| Select bugfixes and enhancements | | All | |||
| Decide on the proposed release blocker | | ||||
| 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 don't need a buildbot for macOS release builds) |
| Windows 32-bit builds | | Build platform: Windows 10 (64-bit), because we use 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) | | All | RC1 (r1844436) was accepted. See the vote resolution below. | ||
Release | Started | Finished | Status | Volunteers | Comments |
| Go / No Go for the release (based on votes and comments) | | Rev. 1844436 will be released. | |||
| Move builds to ASF Dist server (release area) |  | According to the Infrastructure team no special preparations are needed anymore. The Infrastructure team needs to know about an upcoming release to be able to prepare servers and resources and to make sure they are up and running. | |||
| Make sure builds are on the ASF Archive server | | Hash files must not be stored on public servers but only on ASF servers. | |||
| 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's going into a "staged" directory to hide it from the public until the official release date. | |||
Create new SVN tag | | Important Do not create any SVN 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. | |||
QA | Started | Finished | Status | Volunteers | Comments |
| Generic QA | | All | |||
| Specific QA focused on the selected bugfixes/enhancements | | All | |||
Communication | Started | Finished | Status | Volunteers | Comments |
| Blog post: First status update and call for volunteers on dev@ mailing list | - | - | | - | No Pre-Announcements were made. |
| Wiki: Prepare the Release Notes | | Base Note created from 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 | | Marcus Lange | |||
| Website: Update the main AOO test download page | | Marcus Lange | No test links were made. Tests were done only locally. | ||
| 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 needed 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 | | Let's consolidate changes from both persons that were done independently by accident. 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 | | Marcus Lange | Here the large blue headline with "Apache OpenOffice X.Y.Z released" is meant. | ||
| Website: Update the ASF project information | | Marcus Lange | The DOAP RDF data needs to be updated. | ||
| Delete "staged" flag from the new release directory at SourceForge | | ||||
| 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). | |||
| 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@ | | ||||
| Update Feed: New check.Update for the aoo415 area and all older releases | Not before 1-2 weeks after the release. | | 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. | ||
Go-Live | Started | Finished | Status | Volunteers | Comments |
| The release is live | | All | Many thanks to everyone involved! |
Stay Informed
The best channels for accurate information about the release progress are:
- The development mailing list archives
- The Apache OpenOffice official blog
- The Subversion 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 | |||||
| khirano | 1 | 1 | Japanese | |||||||
| Andrea | 1 | 1 | 1 | 1 | Italian | |||||
| Marcus | 1 | 1 | 1 | 1 | US / German | |||||
| Matthias | 1 | 1 | 1 | 1 | 1 | US / German | Included 32 bit Linux | |||
| Josef | 1 | 1 | ||||||||
| Pedro | 1 | 1 | 1 | 1 | US / Portuguese | |||||
| Jim | 1 | 1 | 1 | 1 | 1 | 1 | Included 32 bit Linux | |||
| Summary | 7 | 4 | 4 | 1 | 6 | 3 | 1 | 1 | ||