...
The SVN usage is described in some more details here: https://openoffice.apache.org/source.html. So, just "svn checkout" the relevant branch. Starting with 4.1.3 we have been using dedicated branches, so naming is now obvious (we had been reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1 and 4.1.2). Branches are listed at http https://svn.apache.org/viewvc/openoffice/branches/
$ svn checkout https://svn.apache.org/repos/asf/openoffice/branches/AOO413
...
Build with release options
Use the scripts at http https://svn.apache.org/viewvc/openoffice/devtools/build-scripts/. The 4.1.4 5 scripts are correct.
Release Candidates
...
http://www.apache.org/legal/release-policy.html#release-signing
All files need:
- md5 hash as <filename>.md5
- sha256 hash as <filename>.sha256
- A detached signature as <filename>.asc (see https://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig for details)
- The Release Manager signs the source
- Other packages are signed by the person who provided them
...
Upload builds using svn mv to ASF Dist server (dist area) - the target SVN URL has the pattern https://dist.apache.org/repos/dist/release/openoffice/4.1.4 and this can be done before or after the copy to SourceForge.
IMPORTANT:
The Infrastructure team needs to know about an upcoming release to be able to prepare servers and resources and to make sure they are up and running. Write a mail to infrastructure@apache.org and tell them what can be expected (number of files, total file size, directory structure, etc.). See http://www.apache.org/legal/release-policy.html#heads-up for further details. You have to do this before executing svn mv !
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.
STEP BY STEP: (assuming you updated the ASF dist server first)
1) Open https://sourceforge.net/projects/openofficeorg.mirror/files - Add Folder, name: 4.1.4 and mark it as staged (this will automatically apply to all contents)
2) svn export https://dist.apache.org/repos/dist/release/openoffice/4.1.4 (in case you don't already have a local checkout)
3) Remove all checksums/hashes since we don't want them on third-party servers: find 4.1.4 -type f \( -name *.asc -o -name *.md5 -o -name *.sha256 \) -delete
4) rsync -avz 4.1.4/ username@frs.sourceforge.net:/home/frs/mirror/openofficeorg/4.1.4/
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).
- SourceforgeSourceForge: 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.
...