CiviCRM v5.x.0: Publish a release candidate

Prerequisites

See Prerequisites

All commands need to run in a suitably configured environment.

1: Sanity checks

Note the original branch, such as master.
Note the intended version, such as 5.1 or 5.3. (In the rest of this document, we'll refer to 5.X, but 5.X should be adjusted to circumstance.)
In Jenkins, review the scheduled tests for master and determine if anything should block the RC.

2: Update versions and create branches

We will raise the version numbers and create branches on each CiviCRM repository. The script givi wf:rc performs the necessary updates:

cd ~/src/master
givi wf:rc

TIP: givi can provide a preview (--dry-run aka -N) or an interactive confirmation (--step aka -S).

3: Setup automated processes

Go to https://test.civicrm.org/manage/configure

In "Global Properties => Environment Variables", update the branch/version lists.

ESR_STABLE_RC_MASTER: This should be a list of 4 versions (the ESR, the stable, the RC, and the master/dev)
STABLE_RC_MASTER: This should be a list of 3 versions (the stable, the RC, and the master/dev)
RC_MASTER:This should be a list of 2 versions (the RC and the master/dev).

Explanation: The purpose is to influence the various matrices (which use Dynamic Axis). However, the matrices may not update until the next execution. Some relevant jobs:

4: Publish tarballs

Go to https://test.civicrm.org/job/CiviCRM-Publish/
Check to see if the new branch is being built automatically. If not:
- Login (if you haven't already)
- Click "Build with parameters"
- For the branch name, enter your chosen 5.X.