Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code

StartedFinishedStatusVolunteersComments
Appoint Release Manager(tick)Ariel Constenla-HaileHe was the only candidate
Propose string/localization updates(tick)Ariel Constenla-HaileParticular language changes are considered for 4.1.4
Propose dictionary updates  (tick) Matthias SeidelSee release notes for the list of updated dictionaries 
Select bugfixes and enhancements
 
 (tick)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  (tick)Ariel Constenla-HaileThis is done only by the Release Manager
Provide code for the selected bugfixes/enhancements  (tick)   

Build

StartedFinishedStatusVolunteersComments
Buildbots--(tick)-

Buildbots available for: Windows, Linux, FreeBSD. Mac OS X macOS still missing but not a blocker (we don't need a buildbot for OS X release builds)

Windows 32-bit builds  (tick)

 

Ariel Constenla-Haile

 

Mac OS X macOS 64-bit builds  (tick) Ariel Constenla-Haile 
Linux 32-bit and 64-bit builds  (tick) Ariel Constenla-Haile 
SDK builds  (tick) Ariel Constenla-Haile 
Source builds  (tick)   
Upload builds to ASF Dist server (dev area)  (tick) Ariel Constenla-Haile 
Vote on Release Candidate  (tick)  Ariel Constenla-Haile 
Go / No Go for the release (based on votes and comments)  (tick) Ariel Constenla-Haile 
Upload builds to SF mirrors  (tick)  

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 username@frs.sourceforge.net:/home/frs/mirror/openofficeorg/4.1.4/

Make sure it's going into a "staged" drectory

Move builds to ASF Dist server (dist area)  (tick)   
Make sure builds are on the ASF Archive server  (tick)  Hash files must not be stored on public servers but only on ASF servers
Sourceforge: Update to "Latest Version"  (tick)  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

StartedFinishedStatusVolunteersComments
Generic QA  (tick) All 
Specific QA focused on the selected bugfixes/enhancements  (tick) All 

Communication

StartedFinishedStatusVolunteersComments
Blog post: First status update and call for volunteers on dev@ mailing list  (tick)   
Website: Link top bar hint to the blog post  (tick)   
Wiki: Prepare the Release Notes (tick)Keith McKennaBase note created via template
Translation: Give participants a note so that they can create localized release notes  (tick)   
Website: Update the main AOO test download page  (tick)  Test if the download links are working (binaries, hash files, release notes, etc.)
Website: Update the main AOO download page  (tick)   
Website: Update the project's AOO pages: main and download  (tick)   
Website: Update the ASF project information  (tick)  The DOAP RDF data needs to be updated.
Blog post: Write the announcement to the AOO blog  (tick)   
Announcement: Prepare Apache Press Release  (tick)  

Working together with Sally Khudairi @ Apache, based on Release Notes

Translation: Give participants a note so that they can create localized press release  (tick)   
Announcement: Write official announcement for announce@  (tick)   

Stay Informed

The best channels for accurate information about the release progress are:

...