THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Apache OpenOffice 4.1.5 (AOO 4.1.5) is the next planned release of Apache OpenOffice.
Update: Apache OpenOffice 4.1.5 was released on 30 December 2017. See the Release Notes for more information.
Release Schedule
The release is planned for December 2017.
...
Code | Started | Finished | Status | Volunteers | Comments | ||||
|---|---|---|---|---|---|---|---|---|---|
| Appoint Release Manager | 2016 |  | Jim Jagielski | As per thread on dev@ | |||||
| Propose string/localization updates | 2016 | | Ariel Constenla-Haile | All pertinent bugz blockers closed | |||||
| Propose dictionary updates | 2016 | | Matthias Seidel | Andrea Pescetti | All pertinent bugz blockers closed | ||||
| Select bugfixes and enhancements | 2016 | | All | in process | |||||
| Decide on the proposed release blocker | 2016 | | Jim Jagielski | in process | |||||
| Provide code for the selected bugfixes/enhancements | 2016 | | All | in process | |||||
Build | Started | Finished | Status | Volunteers | Comments | ||||
| Buildbots | - | - | | - | Buildbots available for: Windows , and Linux, FreeBSD. macOS still missing but not a blocker (we don't need a buildbot for OS X OS X release builds) | ||||
| Windows 32-bit builds | | Matthias Seidel | Build platform: Windows 10 (64bit), because we use Windows 64bit shell extensions | ||||||
| macOS 64-bit builds | | Jim Jagielski | Build server: macOS 10.12 (Sierra w/ Xcode7) | ||||||
| Linux 32-bit and 64-bit builds | | Jim Jagielski | CentOS5, both rpm and deb | ||||||
| Source builds | | Jim Jagielski | |||||||
| 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. | |||||||
| Vote on Release Candidate | | Jim Jagielski | |||||||
| Go / No Go for the release (based on votes and comments) | | Jim Jagielski | |||||||
| Move builds to ASF Dist server (dist area) | | Jim Jagielski | Jim forgot to warn Infra. Changed How to Cook a Release to better remind people. | ||||||
| Make sure builds are on the ASF Archive server | | Jim Jagielski | Hash files must not be stored on public servers but only on ASF servers | ||||||
| Upload builds to SF mirrors | | Carl MarcumAndrea Pescetti | 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" drectory | ||||||
| Move builds to ASF Dist server (dist area) | Jim Jagielski | Jim forgot to warn Infra. Changed How to Cook a Release to better remind people. | |||||||
| Make sure builds are on the ASF Archive server | | Jim Jagielski | Hash files must not be stored on public servers but only on ASF serversdirectory to hide it from the public until the official release date. | ||||||
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 | - | - | | - | |||||
| Wiki: Prepare the Release Notes | | Keith McKenna | Keith: Base note created via template Matthias and Marcus: Further work, see here: Release Notesupdates | ||||||
| Translation: Give participants a note so that they can create localized press release | - | - | Heads-Up sent to Joerg Schmidt (de) | Marcus Lange | Done by private mail | - | It was agreed that no press release will be done | ||
| Announcement: Prepare Apache Press Release | - | - | | Marcus Lange | - | It was agreed that no press release will be doneWorking together with Sally Khudairi @ Apache, based on Release Notes | |||
| Translation: Give participants a note so that they can create localized release notes | de: nl: |
| | Keith McKenna | Done by mail on @L10nDone by private mails | ||||
| Website: Update the main AOO test download page | - | - | | Marcus Lange- | Test if the download links are working (binaries, hash files, release notes, etc.) and the metadata (milestone, build, SVN rev., release date) are correct. | ||||
| Website: Update the main AOO download page | | Marcus Lange | After the test was successful, do the changes in the Life-System. Test again that the links are working and the metadata is correct. | ||||||
| Website: Update the localized download pages. | | 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 | | Matthias SeidelMarcus Lange | 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 | | Matthias Seidel | 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. | ||||||
| Sourceforge: Update to "Latest Version" | | Marcus Lange | Set the attribute "Latest Version" to all full installation files for every platformWindows, macOS and Linux (see the icons for the correct checkbox). | ||||||
| Blog post: Write the announcement to the AOO blog | | Marcus Lange | |||||||
| Announcement: Write official announcement for announce@apache.openoffice.org | | Marcus Lange | |||||||
| Announcement: Copy the official announcement for announce@apache.org | | Marcus Lange | Important | ||||||
| Forward the announcement to dev@ | | Marcus Lange | |||||||
| Update Feed: New check.Update for the aoo413 aoo414 area | Users of AOO 4.0 - 4.1.4 will receive update notification, macOS is temporarily disabled. | and all older releases | Andrea Pescetti | 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 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 |
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
...