...

• Pick a Release Manager, by lazy consensus unless there are multiple candidates.
• Create an a SVN branch from a previous branch or from trunk. This has to be discussed and agreed on the dev@ mailing list.
• Select issues and enhancements to go in the releases that can be accepted as a release blocker.
• Only the Release Manager should grant or deny requested issues:
  • This is done by setting the release blocker flag in the respective Bugzilla (BZ ) issue (? = ask for blocker, + = grant as blocker, - = deny as blocker).
  • See BZ 127103 as example.

...

• Select bugfixes and enhancements.
• Issues that are seen as release blocker:
  
  • They need to be discussed. Ideally, this takes place publicly on dev@, but security fixes must be discussed on a private mailing list.
  • Write something about why it is valid as blocker (problem situation, what needs to be fix in code, what is the risk when fixed/not fixed).

Create new SVN tag

1. Double-check what version was built (for 4.1.3 it's Rev. 1761381, you find it even in the About Box); of course, if this happens during the release process, the Release Manager knows it.
2. Find the relevant branch in http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's AOO413 and revision number is indeed 1761381) and check it is aligned (it is, since the two revisions match).
3. SVN copy the branch to the tag. You can do it locally but it's much more efficient to do it remotely. So, from anywhere on a machine with SVN access, just run:

...

...

• • ).

Check out the source code

...

• Upload 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.3/
  IMPORTANT:
  Make sure it's going into a "staged" drectory.
  
  
• Upload builds to ASF Dist server (dist area)
• Make sure builds are on the ASF Archive server
  NOTE:
  Hash files must not be stored on public servers but only on ASF servers. The files get copied automatically when the files get uploaded to the ASF Dist server (dist area).
  
  
• 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 aoo<version> 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.

Create new SVN tag

1. Double-check what version was built (for 4.1.3 it's Rev. 1761381, you find it even in the About Box); of course, if this happens during the release process, the Release Manager knows it.
2. Find the relevant branch in http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's AOO413 and revision number is indeed 1761381) and check it is aligned (it is, since the two revisions match).
3. SVN copy the branch to the tag. You can do it locally but it's much more efficient to do it remotely. So, from anywhere on a machine with SVN access, just run:

$ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413 https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO revision \
1761381 from branch AOO413 was voted to be released as Apache OpenOffice 4.1.3 in October 2016" 

Committed revision 1790662. 

This results in the new tag appearing at http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the missing 4.1.3 tag, so I did run the command above).

Communication

Pre-Announcement

...