5.0.0-beta2 release setup

[jamoore]

This ticket is a follow-up to #10788

---

During the build

• Check if submodule pointers have been updated
• Rename jobs to:
  • OME4.4-release
  • OME5.0-release

On promote

• $RELEASE/ and $RELEASE.html should be made read-only

On reject

• $RELEASE/ and $RELEASE.html should be deleted.
• Tags should be removed from snoopy

Other builds to integrate

• C++
• Maven

Other TODOs

• Migrate all cvs/snapshots directories to downloads.o.org
• Generate more elaborate index pages (possibly using pelican)
• Migrate whats-new to individual repos. See #10788's description
• Re-activate link checking in ome-release.git
• Unzip Sphinx and API docs
• Add job to:
  • Check git status in download directories
  • Check (~~read-only~~ OR .htaccess)

[sbesson]

Added a set of four jobs for performing 5.0 release ​OMERO-5.0-release ​OMERO-5.0-download-page/ ​BIOFORMATS-5.0-release ​BIOFORMATS-5.0-download-page

Backported OMERO downloads pages from 4.4.9 and opened PR against ome-releas: ​https://github.com/openmicroscopy/ome-release/pull/29.

Bio-Formats downloads page redesign has been moved to a specific ticket #11651

[sbesson]

All release jobs have been renamed with explicit major and minor version numbers and a PR has been opened to document these new names in the release process page ​https://github.com/openmicroscopy/ome-internal/pull/73

[sbesson]

Logic has been added to all the OMERO and Bio-Formats downloads page jobs to

1. reset write permissions files at the beginning of the job to index.html OR index-staging.html and images/ folder
2. generate the downloads page and copy them to the release folder
3. recursively set read-only permissions to the entire release folder

Similar permissions management steps will be implemented for the OMERO/Bio-Formats jobs if this makes sense.

[sbesson]

The modifications from the last comment have been removed as it allowed the jobs to easily overwrite data. The permissions setting/unsetting step needs to be either manual or done in a promotion step with external validation.

A new job ​OME-release-check has been set up to check read-only permissions and git status on the downloads directories. Future improvements of tho job will be to

• alternately check for .htaccess or read-only permission
• convert the console output into parable warnings and create unstable builds if applicable

[jamoore]

Release job used for beta2-rc3 successfully. All remaining TODOs migrated to trello.