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

Update Release Checklist

Browse Source 
Remove To Do list (which didn't get discussed).
Add stuff about submodule versions and pushing tags.
List invididual module version number files to be updated at
final release time.
This commit is contained in:
Andrew Johnson
2018-12-17 16:39:09 -06:00
parent cff13b9aa7
commit 6ee928109c
1 changed files with 30 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
documentation/ReleaseChecklist.html
View File

@ -248,24 +248,6 @@ made.</p>
</td>
</tr>
<tr>
<th colspan="3">To Do</th>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Discuss and resolve before final release:
<ul>
<li>Update version numbers in individual
<tt>modules/*/configure/*VERSION</tt> files?</li>
<li>Unifying module Release Notes for easier publication.</li>
<li>Unifying module documentation directories and Doxygen
config's.</li>
<li>Publishing releases on the new website.</li>
</ul>
</td>
</tr>
<tr>
<th colspan="3">Release Approval</th>
</tr>
@ -282,18 +264,36 @@ made.</p>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Edit and commit changes to the EPICS version number file
configure/CONFIG_BASE_VERSION.</td>
<td>
<p>For each external submodule, check if the module's release version
number (and SHRLIB_VERSION setting) has been updated if appropriate,
and that its Release Notes have been updated to cover any changes.
Commit any fixes and tag the module if that hasn't already been
done.</p>
<p>Update all external submodules on the Base-7.0 branch and
commit.</p></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Tag the module in Git:
<td>Edit and commit changes to the EPICS Base version number file and
the embedded module version files:
<ul>
<li>configure/CONFIG_BASE_VERSION </li>
<li>modules/libcom/configure/CONFIG_LIBCOM_VERSION</li>
<li>modules/ca/configure/CONFIG_CA_VERSION</li>
<li>modules/database/configure/CONFIG_DATABASE_VERSION</li>
</ul></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Tag the epics-base module in Git:
<blockquote><tt>
cd base-7.0<br />
git tag -m 'ANJ: Tagged for 7.0.2' R7.0.2</i>
</tt></blockquote>
</td>
Don't push the new tag to the Launchpad repository yet.</td>
</tr>
<tr>
<td>&nbsp;</td>
@ -315,7 +315,12 @@ made.</p>
<td>&nbsp;</td>
<td>Release Manager</td>
<td>Test the tar file by extracting its contents and building it on at
least one supported platform</td>
least one supported platform. When this succeeds the new git tag can be
pushed to the Launchpad repository:
<blockquote><tt>
git push --follow-tags upstream 7.0
</tt></blockquote>
</td>
</tr>
<tr>
<td>&nbsp;</td>
@ -335,8 +340,8 @@ made.</p>
<tr>
<td>&nbsp;</td>
<td>Website Manager</td>
<td>Copy the tar file and its <tt>.asc</tt> signature file to the Base
download area of the website.</td>
<td>Upload the tar file and its <tt>.asc</tt> signature file to the
Launchpad milestone for this release version.</td>
</tr>
<tr>
<td>&nbsp;</td>