Versions Compared

Old Version 3

changes.mady.by.user Matthias Seidel

Saved on

compared with

New Version 4

changes.mady.by.user Keith McKenna

Saved on

Key

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

...

Code

StartedFinishedStatusVolunteersComments
Appoint Release Manager

 
(tick)

Peter Kovacs

He was the only volunteer
Propose string/localization updates


 
Propose dictionary updates




Select bugfixes and enhancements


All


Decide on the proposed release blocker




Provide code for the selected bugfixes/enhancements


All

Build

StartedFinishedStatusVolunteersComments
Buildbots--(tick)-

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

Windows 32-bit builds


Matthias Seidel

Build platform: Windows 10 (64-bit), because we use Windows 64-bit 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
CentOS 5, both rpm and deb
Source builds


Peter Kovacs

 
Upload builds to ASF Dist server (dev area)


Jim Jagielski

Matthias Seidel

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 

All 
Go / No Go for the release (based on votes and comments)


Peter Kovacs

 
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

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

Make sure it's going into a "staged" directory to hide it from the public until the official release date.

QA

StartedFinishedStatusVolunteersComments
Generic QA


All 
Specific QA focused on the selected bugfixes/enhancements


All 

Communication

StartedFinishedStatusVolunteersComments
Blog post: First status update and call for volunteers on dev@ mailing list




Wiki: Prepare the Release Notes



AllBase Note created from template
Translation: Give participants a note so that they can create localized press release




Announcement: Prepare Apache Press Release




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.) and the metadata (milestone, build, SVN rev., release date) are correct.
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.



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



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



Here the large blue headline with "Apache OpenOffice X.Y.Z released" is meant.
Website: Update the ASF project information



The DOAP RDF data needs to be updated.
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





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

StartedFinishedStatusVolunteersComments
The release is live


All 

...