Any patch files linked below should be applied at the root of the -base-3.15.5 tree. Download them, then use the GNU Patch program as +base-3.15.6 tree. Download them, then use the GNU Patch program as follows:
-% cd /path/to/base-3.15.5 +% cd /path/to/base-3.15.6 % patch -p0 < /path/to/file.patchThe following significant problems have been reported with this diff --git a/documentation/README.1st b/documentation/README.1st index 8349d445c..3122bdfbd 100644 --- a/documentation/README.1st +++ b/documentation/README.1st @@ -1,6 +1,6 @@ Installation Instructions - EPICS Base Release 3.15.5 + EPICS Base Release 3.15.6 -------------------------------------------------------------------------- diff --git a/documentation/README.html b/documentation/README.html index eef83ed58..fadca3d11 100644 --- a/documentation/README.html +++ b/documentation/README.html @@ -9,7 +9,7 @@
Installation Instructions
-EPICS Base Release 3.15.5
+EPICS Base Release 3.15.6
Table of Contents
diff --git a/documentation/ReleaseChecklist.html b/documentation/ReleaseChecklist.html index 77917b99e..4b9b55c4b 100644 --- a/documentation/ReleaseChecklist.html +++ b/documentation/ReleaseChecklist.html @@ -41,11 +41,12 @@ that should be performed when creating new releases of EPICS Base. 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. +be made at 2-weekly intervals during the testing and debugging period, and will +be designated as either pre-release versions or Release Candidates 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
@@ -56,7 +57,7 @@ relevent roles unless the Release Manager designates otherwise:
- Release Manager (Ralph Lange)
- 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.
@@ -135,17 +136,17 @@ relevent roles unless the Release Manager designates otherwise:Tag the module in Bazaar, using these tag conventions: @@ -157,14 +158,14 @@ relevent roles unless the Release Manager designates otherwise:
- - R3.15.5-pren + R3.15.6-pre1 — pre-release tag
- - R3.15.5-rcn - — release candidate tag, note the rc is now - lower-case
+ R3.15.6-rc1 + — release candidate tag +cd ~/base/mirror-3.15
- bzr tag R3.15.5-rcn + bzr tag R3.15.6-rc1cd ~/baseCreate a GPG signature file of the tarfile as follows:
bzr export - --root=base-3.15.5-rcn - -r tag:R3.15.5-rcn - base-3.15.5-rcn.tar.gz + --root=base-3.15.6-rc1 + -r tag:R3.15.6-rc1 + base-3.15.6-rc1.tar.gz mirror-3.15- gpg --armor --sign --detach-sig base-3.15.5-rcn.tar.gz + gpg --armor --sign --detach-sig base-3.15.6-rc1.tar.gz@@ -276,7 +277,7 @@ relevent roles unless the Release Manager designates otherwise:Tag the module in Bazaar: @@ -288,14 +289,14 @@ relevent roles unless the Release Manager designates otherwise:cd ~/base/mirror-3.15
- bzr tag R3.15.5 + bzr tag R3.15.6cd ~/baseCreate a GPG signature file of the tarfile as follows:
bzr export - --root=base-3.15.5 - -r tag:R3.15.5 - base-3.15.5.tar.gz + --root=base-3.15.6 + -r tag:R3.15.6 + base-3.15.6.tar.gz mirror-3.15- gpg --armor --sign --detach-sig base-3.15.5.tar.gz + gpg --armor --sign --detach-sig base-3.15.6.tar.gz@@ -305,14 +306,24 @@ 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 and its .asc signature file to the Base + Copy the tar file and its .asc signature file to the Base download area of the website. @@ -343,24 +354,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.