ReleaseChecklist.html,v 1.1.2.8 2008/06/09 21:17:16 anj Exp
This document describes the procedures and provides a checklist of tasks that should be performed when creating new releases of EPICS Base.
The version released on the Feature Freeze date is designated the first 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.
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:
Check | Who | Description |
---|---|---|
Preparing for a release | ||
Release Manager | 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. | |
Release Manager | Set the Feature Freeze date, by which time all CVS commits for enhancements and new functionality should have been completed. After this date, commits should only be made to fix problems that show up during testing. | |
Release Manager & all developers |
Ensure that documentation will be updated before the release date:
|
|
Creating pre-release and Release Candidate versions | ||
Configuration Manager | Edit and commit changes to the EPICS version number file configure/CONFIG_BASE_VERSION. | |
Configuration Manager | Tag the module in CVS. Pre-release version tags take the form Rx-y-z-pren while Release Candidate tags take the form Rx-y-z-RCm. | |
Configuration Manager | Export the tagged version and create a tarfile of the result:
cvs export -kv -d base-x.y.z-pre1 -r Rx-y-z-pre1 epics/base |
|
Configuration Manager | Test the tarfile by extracting its contents and building it on at least one supported platform | |
Configuration Manager | Copy the tar file to the Base download area of the website | |
Website Manager | Create or update a website subdirectory to hold the release documentation, and copy in the files from the base/documentation directory of the tarfile. | |
Website Manager | Create or modify the webpage for the new release with links to the release documents and tar file. Pre-release and RC versions should use the page and URL for the final release version number. | |
Website Manager | Add the new pre-release tar file to the website Base download index page. | |
Testing | ||
Platform Developers | Run the built-in test programs on all available host platforms using
make -s runtests |
|
Platform Developers | Run the CA client side regression tests on all available host platforms. | |
Platform Developers | Build and run the IOC Soft-Test suite 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. setting STATIC_BUILD=YES in configure/CONFIG_SITE. | |
Platform Developers | Build the SNL Sequencer against this version of Base, and check that the makeBaseApp example builds and runs correctly with it. | |
Application Developers | Build external applications against this version of Base on all available platforms and test as appropriate. Application code changes may be necessary where the EPICS Base APIs have been modified. | |
Release Manager | Check that documentation has been updated:
|
|
Release Approval | ||
Release Manager | Obtain a positive Ok to releasefrom all platform developers when a Release Candidate version has gone a whole week without any issues being reported. |
|
Creating the final release version | ||
Configuration Manager | Edit and commit changes to the EPICS version number file configure/CONFIG_BASE_VERSION. | |
Configuration Manager | Tag the module in CVS. Official base release version tags take the form Rx-y-z[-n] | |
Configuration Manager | Export the tagged version and create a tarfile of the result:
cvs export -kv -d base-x.y.z -r Rx-y-z epics/base |
|
Configuration Manager | Test the tar file by extracting its contents and building it on at least one supported platform | |
Configuration Manager | Copy the tar file to the Base download area of the website | |
Website Manager | Update the website subdirectory that holds the release documentation, and copy in the files from the base/documentation directory of the tarfile. | |
Website Manager | Update the webpage for the new release with links to the release documents and tar file. | |
Announce it | ||
Website Manager | Add the new release tar file to the website Base download index page. | |
Website Manager | Link to the release webpage from other relevent areas of the website - update front page and sidebars. | |
Website Manager | Add the new Version number to the Mantis bug tracker. | |
Website Manager | Close all Mantis bug reports that were marked as resolved and which have been fixed in this release. | |
Release Manager | Email tech-talk | |
Website Manager | Add an entry to the website News page, linking to the new version webpage. |