Page History

...

RSCREVISION
BUILD
LAST_MINOR

QA

• Generic QA
  TBD
  
  
• Specific QA focused on the selected bugfixes/enhancements
  TBD

...

• Upload builds using svn mv to ASF Dist server (dist release area) - the target SVN URL has the pattern https://dist.apache.org/repos/dist/release/openoffice/4.1.68 and this can be done before or after the copy to SourceForge (Example: svn mv https://dist.apache.org/repos/dist/dev/openoffice/4.1.8-RC3 https://dist.apache.org/repos/dist/release/openoffice/4.1.8)

• Since 2017, OpenOffice is not on the Apache mirrors anymore. It it unlikely that the Infrastructure team will change that. But when OpenOffice is back on the Apache mirrors, then the Infrastructure team needs to know about the new release and the following notification is becoming a MUST DO again:

  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 move !
  
  

• Upload to SourceForge 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, e.g., username@frs.sourceforge.net:/home/frs/mirror/openofficeorg/4.1.68/.

  IMPORTANT

  Make sure it's going into a "staged" directory.

  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.6 8 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.68 (in case you don't already have a local checkout)

  3) Remove all checksums/hashes/SVN internal files since we don't want them on third-party servers:

  $ rsync -avz --exclude '*.asc' --exclude '*.sha256' --exclude '*.sha512' --exclude '*.svn' 4.1.6/ username@frs.sourceforge.net:/home/frs/mirror/openofficeorg/4.1.6/
  
  

• 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 SourceForge 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.

...

en-US, fr, de, it, es, ja, ru, pl, nl, zh-twTW, cs, zh-cnCN, el, pt, da, no

Do not forget the template files with code "xx".

...

Update the data of the following file: https://svngithub.com/apache.org/repos/asf/openoffice-project/siteblob/trunkmain/content/doap_openoffice.rdf

Finally, don't forget to publish the websiteThis file is located on the project website, which is self-publishing. Just make sure you do the changes in one commit.

IMPORTANT

The new data is not shown after it was published. There is a delay due to a cron job that runs maybe every 24h.

...

• Add all build files as separate lines to a new file. Example for 4.1.6 : https://svn.apache.org/repos/asf/openoffice/devtools/aoo-stats/416.lst
• Add all build files a s as separate lines to : https://svn.apache.org/repos/asf/openoffice/devtools/aoo-stats/all.lst
• Add the new release version values to : https://svn.apache.org/repos/asf/openoffice/devtools/aoo-stats/detail-by-day.py
  • Example for 4.1.6:

  • columns = [ ... , "count_416" , ... ]

  • patternDict = { ... , "count_416" : "4.1.6" , ... }

...

1. Double-check what version was built (for 4.1.6 it is revision 1844436, 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 https://svn.apache.org/viewvc/openoffice/branches/ (in this case it is AOO416 and revision number is indeed 1844436) and check it is aligned (it is, since the two revisions match).
3. SVN will copy the branch to the tag. You can do it locally but it is 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/AOO413AOO416 https://svn.apache.org/repos/asf/openoffice/tags/AOO413AOO416 -m "AOO revision \
1844436 from branch AOO416 was voted to be released as Apache OpenOffice 4.1.6 on November, 18th, 2018" 

Committed revision 1844437. 

...