epics/epics-base
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Update Release Checklist

Browse Source
This commit is contained in:
Andrew Johnson
2017-01-30 18:04:47 -06:00
parent 051c059938
commit a7f0525ac7
1 changed files with 42 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

81
documentation/ReleaseChecklist.html
View File

@ -38,25 +38,24 @@ that should be performed when creating production releases of EPICS Base.</p>
<h3>The Release Process</h3>
<p>The version released on the Feature Freeze date is designated the first
pre-release, <tt>-pre1</tt>. The first Release Candidate <tt>-rc1</tt> is the
pre-release, <tt>-pre1</tt>. The first release candidate <tt>-rc1</tt> 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.</p>
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.</p>
<h3>Roles</h3>
<p>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:</p>
<p>The following roles are used below:</p>
<dl>
<dt><strong>Release Manager</strong> (Ralph Lange)</dt>
<dt><strong>Release Manager</strong> ()</dt>
<dd>Responsible for managing and tagging the release</dd>
<dt><strong>Platform Developers</strong></dt>
<dt><strong>Platform Developers</strong> (optional)</dt>
<dd>Responsible for individual operating system platforms</dd>
<dt><strong>Application Developers</strong></dt>
<dd>Responsible for support modules that depend on EPICS Base.</dd>
@ -140,12 +139,12 @@ relevent roles unless the Release Manager designates otherwise:</p>
</li>
<li>
<tt>R3.16.1-rc<i>n</i></tt>
&mdash; release candidate tag, note the <tt>rc</tt> is now
lower-case</li>
&mdash; release candidate tag
</li>
</ul>
<blockquote><tt>
cd ~/base/mirror-3.16<br />
bzr tag R3.16.1-rc<i>n</i>
bzr tag R3.16.1-rc1
</tt></blockquote>
</td>
</tr>
@ -156,14 +155,16 @@ relevent roles unless the Release Manager designates otherwise:</p>
generates a gzipped tarfile directly from the repository:
<blockquote><tt>
cd ~/base<br />
bzr export --keywords=publish
--root=base-3.16.1-rc<i>n</i>
-r tag:R3.16.1-rc<i>n</i>
base-3.16.1-rc<i>n</i>.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
</tt></blockquote>
This requires that the Bazaar keywords plugin is installed and
configured properly.
Create a GPG signature file of the tarfile as follows:
<blockquote><tt>
gpg --armor --sign --detach-sig base-3.16.1-rc1.tar.gz
</tt></blockquote>
</td>
</tr>
<tr>
@ -256,7 +257,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Obtain a positive <q>Ok to release</q> 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.</td>
</tr>
<tr>
@ -285,14 +286,16 @@ relevent roles unless the Release Manager designates otherwise:</p>
generates a gzipped tarfile directly from the repository:
<blockquote><tt>
cd ~/base<br />
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
</tt></blockquote>
This requires that the Bazaar keywords plugin is installed and
configured properly.
Create a GPG signature file of the tarfile as follows:
<blockquote><tt>
gpg --armor --sign --detach-sig base-3.16.1.tar.gz
</tt></blockquote>
</td>
</tr>
<tr>
@ -301,14 +304,25 @@ relevent roles unless the Release Manager designates otherwise:</p>
<td>Test the tar file by extracting its contents and building it on at
least one supported platform</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Upload the release tar file to the Launchpad download area.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Find all Launchpad bug reports with the status Fix Committed which
have been fixed in this release and mark them Fix Released.</td>
</tr>
<tr>
<th colspan="3">Publish and Announce it</th>
</tr>
<tr>
<td>&nbsp;</td>
<td>Website Manager</td>
<td>If necessary recreate the tarfile following the instructions above.
Copy the tar file to the Base download area of the website</td>
<td>Copy the tar file and its <tt>.asc</tt> signature file to the Base
download area of the website.</td>
</tr>
<tr>
<td>&nbsp;</td>
@ -338,24 +352,13 @@ relevent roles unless the Release Manager designates otherwise:</p>
<tr>
<td>&nbsp;</td>
<td>Website Manager</td>
<td>Upload the release tar file to the Launchpad download area.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Website Manager</td>
<td>Find all Launchpad bug reports with the status Fix Committed which
have been fixed in this release and mark them Fix Released.</td>
<td>Add an entry to the website News page, linking to the new version
webpage.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Email tech-talk</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Website Manager</td>
<td>Add an entry to the website News page, linking to the new version
webpage.</td>
<td>Announce the release on the tech-talk mailing list.</td>
</tr>
</tbody>
</table>