From a7f0525ac764ab8b62beb8c2c208a807e93b67f7 Mon Sep 17 00:00:00 2001 From: Andrew Johnson Date: Mon, 30 Jan 2017 18:04:47 -0600 Subject: [PATCH] Update Release Checklist --- documentation/ReleaseChecklist.html | 81 +++++++++++++++-------------- 1 file changed, 42 insertions(+), 39 deletions(-) diff --git a/documentation/ReleaseChecklist.html b/documentation/ReleaseChecklist.html index 0a2cdab5f..1cc67794c 100644 --- a/documentation/ReleaseChecklist.html +++ b/documentation/ReleaseChecklist.html @@ -38,25 +38,24 @@ that should be performed when creating production releases of EPICS Base.

The Release Process

The version released on the Feature Freeze date is designated the first -pre-release, -pre1. The first Release Candidate -rc1 is the +pre-release, -pre1. The first release candidate -rc1 is the first version that has undergone widespread testing and which has no known problems in it that are slated to be fixed in this release. New versions should be made at about weekly intervals during the testing and debugging period, and -will be designated as either pre-release versions or Release Candidates by the -Release Manager. A Release Candidate that has received widespread testing for a -week without any additional problems being discovered or significant changes -being committed can be designated as the final release version.

+will be designated as either pre-release or release candidate versions by the +Release Manager. After a release candidate has been available to the whole +community for testing for at least a week without any additional problems being +reported or significant changes being committed, the branch can be designated as +the final release version.

Roles

-

The following roles are required. The individuals named here have have been -responsible for these tasks in the past and are expected to continue in the -relevent roles unless the Release Manager designates otherwise:

+

The following roles are used below:

-
Release Manager (Ralph Lange)
+
Release Manager ()
Responsible for managing and tagging the release
-
Platform Developers
+
Platform Developers (optional)
Responsible for individual operating system platforms
Application Developers
Responsible for support modules that depend on EPICS Base.
@@ -140,12 +139,12 @@ relevent roles unless the Release Manager designates otherwise:

  • R3.16.1-rcn - — release candidate tag, note the rc is now - lower-case
    • + — release candidate tag +
    cd ~/base/mirror-3.16
    - bzr tag R3.16.1-rcn + bzr tag R3.16.1-rc1
    @@ -156,14 +155,16 @@ relevent roles unless the Release Manager designates otherwise:

    generates a gzipped tarfile directly from the repository:
    cd ~/base
    - bzr export --keywords=publish - --root=base-3.16.1-rcn - -r tag:R3.16.1-rcn - base-3.16.1-rcn.tar.gz + bzr export + --root=base-3.16.1-rc1 + -r tag:R3.16.1-rc1 + base-3.16.1-rc1.tar.gz mirror-3.16
    - This requires that the Bazaar keywords plugin is installed and - configured properly. + Create a GPG signature file of the tarfile as follows: +
    + gpg --armor --sign --detach-sig base-3.16.1-rc1.tar.gz +
    @@ -256,7 +257,7 @@ relevent roles unless the Release Manager designates otherwise:

      Release Manager Obtain a positive Ok to release from all platform developers - once a Release Candidate version has gone a whole week without any + once a release candidate version has gone a whole week without any issues being reported. @@ -285,14 +286,16 @@ relevent roles unless the Release Manager designates otherwise:

    generates a gzipped tarfile directly from the repository:
    cd ~/base
    - bzr export --keywords=publish + bzr export --root=base-3.16.1 -r tag:R3.16.1 base-3.16.1.tar.gz mirror-3.16
    - This requires that the Bazaar keywords plugin is installed and - configured properly. + Create a GPG signature file of the tarfile as follows: +
    + gpg --armor --sign --detach-sig base-3.16.1.tar.gz +
    @@ -301,14 +304,25 @@ relevent roles unless the Release Manager designates otherwise:

    Test the tar file by extracting its contents and building it on at least one supported platform + +   + Release Manager + Upload the release tar file to the Launchpad download area. + + +   + Release Manager + Find all Launchpad bug reports with the status Fix Committed which + have been fixed in this release and mark them Fix Released. + Publish and Announce it   Website Manager - If necessary recreate the tarfile following the instructions above. - Copy the tar file to the Base download area of the website + Copy the tar file and its .asc signature file to the Base + download area of the website.   @@ -338,24 +352,13 @@ relevent roles unless the Release Manager designates otherwise:

      Website Manager - Upload the release tar file to the Launchpad download area. - - -   - Website Manager - Find all Launchpad bug reports with the status Fix Committed which - have been fixed in this release and mark them Fix Released. + Add an entry to the website News page, linking to the new version + webpage.   Release Manager - Email tech-talk - - -   - Website Manager - Add an entry to the website News page, linking to the new version - webpage. + Announce the release on the tech-talk mailing list.