EPICS Base Release Procedures Checklist

ReleaseChecklist.html,v 1.1.2.4 2003/09/19 18:36:54 jba Exp

This document is a checklist of things that must be done when creating a new release of EPICS Base. Additions and ammendments to this list are welcome.

The following roles are used, in addition to the names of individuals who have been responsible for specific tasks in the past:

Release Manager
Responsible for the release
Platform Developers
Responsible for individual operating system platforms

Check Who Description
Preparing for a release
  Marty Kraimer Email all developers about the upcoming release and ask for a list of remaining jobs that must be finished.
  All developers Check the Mantis bug tracker for any outstanding items and handle appropriately. All bugs that have been fixed should have been marked as resolved.
  Marty Kraimer Set a date by which all CVS commits must be done, after which commits should only be to fix problems that show up during Final Testing.
  Release Manager Ensure that documentation will be updated before the release date:
  • Application Developers Guide
  • Release Notes
  • Known Problems
  • Other documents
  ? ...
Final testing
  Platform Developers Run the Soft IOC tests in mrkSoftTest on all available platforms.
  Platform Developers Check that all makeBaseApp templates build and run properly, all xxxApp and xxxBoot types and any internal options, e.g. standalone sncExample appliction, STATIC_BUILD=YES.
  Marty Kraimer Run the VME I/O tests in mrkHwdTest on all available vxWorks VME platforms.
  Jeff Hill Run the CA client side regression tests on all available host platforms.
  ? ...
Release Approval
  Release Manager Obtain a positive 'Ok to release' from all platform developers.
Make the release
  Janet Anderson Edit and commit changes to the EPICS version number files, config/CONFIG_BASE_VERSION and configure/CONFIG_BASE_VERSION.
  Janet Anderson Tag the module in CVS. Version tags take the form Rx-y-z[-{alpha,beta,n}]
  Janet Anderson Export the tagged version, "cvs export -kv -d base-x.y.z -r Rx-y-zepics/base", and create the baseRx.y.z[{alpha,beta}n].tar.gz file of the result
  Janet Anderson Test the tar file by extracting its contents and building it on at least one supported platform
  Janet Anderson Copy the tar file to the Base download area of the website
  Andrew Johnson Create a new website subdirectory to hold the release documentation, and copy in the files from the base/documentation directory of the tarfile
  Andrew Johnson Create a webpage for the new release with links to the release documents and tar file
  ? ...
Announce it
  Andrew Johnson Add the new release tar file to the website Base download index page
  Andrew Johnson Link to the release webpage from other relevent areas of the website - update front page and sidebars
  Andrew Johnson Add the new Version number to the Mantis bug tracker
  Andrew Johnson Close all Mantis bug reports that were marked as resolved and which have been fixed in this release
  Release Manager Email tech-talk
  Andrew Johnson Add an entry to the website News page, linking to the new webpage
  ? ...