Apache OpenOffice 4.1.4 (AOO 4.1.4) is the next planned release of Apache OpenOffice.
Release Schedule
The exact release date is TBD.
Release Progress and Volunteers
Code | Started | Finished | Status | Volunteers | Comments |
---|---|---|---|---|---|
Appoint Release Manager | Ariel Constenla-Haile | He was the only candidate | |||
Propose string/localization updates | Ariel Constenla-Haile | Particular language changes are considered for 4.1.4 | |||
Propose dictionary updates | |||||
Select bugfixes and enhancements | All | Anyone can propose a blocker either using the "4.1.4 Release Blocker" flag in Bugzilla or writing to the dev list | |||
Decide on the proposed release blocker | Ariel Constenla-Haile | This is done only by the Release Manager | |||
Provide code for the selected bugfixes/enhancements | |||||
Build | Started | Finished | Status | Volunteers | Comments |
Buildbots | - | - | - | Buildbots available for: Windows, Linux, FreeBSD. Mac OS X still missing but not a blocker (we don't need a buildbot for OS X release builds) | |
Windows builds | Ariel Constenla-Haile |
| |||
Mac OS X 64-bit builds | Ariel Constenla-Haile | ||||
Linux 32-bit and 64-bit builds | Ariel Constenla-Haile | ||||
SDK builds | Ariel Constenla-Haile | ||||
Source builds | |||||
Upload builds to ASF Dist server (dev area) | Ariel Constenla-Haile | ||||
Vote on Release Candidate | Ariel Constenla-Haile | ||||
Go / No Go for the release (based on votes and comments) | Ariel Constenla-Haile | ||||
Upload builds to SF 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" drectory | ||||
Move builds to ASF Dist server (dist area) | |||||
Make sure builds are on the ASF Archive server | Hash files must not be stored on public servers but only on ASF servers | ||||
Sourceforge: Update to "Latest Version" | Set the attribute "Latest Version" to all full installation files for every platform | ||||
Update Feed: New check.Update for the aoo414 area |
| 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. | |||
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 | |||||
Website: Link top bar hint to the blog post | |||||
Wiki: Prepare the Release Notes | |||||
Translation: Give participants a note so that they can create localized release notes | |||||
Website: Update the main AOO test download page | Test if the download links are working (binaries, hash files, release notes, etc.) | ||||
Website: Update the main AOO download page | |||||
Website: Update the project's AOO pages: main and download | |||||
Website: Update the ASF project information | The DOAP RDF data needs to be updated. | ||||
Blog post: Write the announcement to the AOO blog | |||||
Announcement: Prepare Apache Press Release | Working together with Sally Khudairi @ Apache, based on Release Notes | ||||
Translation: Give participants a note so that they can create localized press release | |||||
Announcement: Write official announcement for announce@ |
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 developement is actually done