hypre/releases/check1.14.0b.txt
falgout 5ff4dc0775 Committing final certification for 1.14.0b release.
Deleted "check out tagged version" in the various checklist files.
2006-12-04 16:30:34 +00:00

82 lines
2.1 KiB
Plaintext

HYPRE Beta Release Checklist
Beta releases tend to occur somewhat frequently. They may include new
technology, but they are reasonably stable.
The following steps must be completed, initialed & dated on the --->> line by
the responsible project member before the release is made available to users.
1. Decision made for release number: 1.14.0b
--->> rdf 11/30/2006
2. Copy this file to 'check{release number}.txt' and commit to the repository
--->> rdf 11/30/2006
3. Project personnel advised of release decision and tentative date with
a request to not disrupt the repository until the release is complete
--->> rdf 11/30/2006
4. Update CHANGELOG file with information regarding contents of this release
--->> rdf 11/30/2006
5. Verify that user, reference, and developer manuals are updated
--->> n/a
6. Verify that all agreed-upon changes have been committed
--->> rdf 11/30/2006
7. Project Lead review and/or concurrence to release
--->> rdf 11/30/2006
8. Update config/configure.in with release number and date, then run
config/bootstrap and commit changes to the repository
--->> rdf 11/30/2006
9. Tag repository with release number
--->> rdf 11/30/2006
10. Checkout tagged version
--->> skipped
11. Manually run the autotest script with the following options on the checked
out version: -tux149 -insure -gpsmp -pengra
--->> skipped (relying on runs prior to tagging)
12. If the test runs properly, proceed. Otherwise, untag the repository, make
necessary corrections, and return to step 8.
--->> rdf 11/30/2006
13. Create release tar file by running the mkdist script './mkdist [VersionID]'
(this can be run from within any directory, just be sure to use the latest
version of the 'mkdist' script)
--->> rdf 11/30/2006
14. On the CASC cluster, copy tar file to /usr/casc/hypre
--->> rdf 11/30/2006
15. Put release on download page, and inform project team and other appropriate
users of availability
--->> rdf 12/04/2006
16. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository
--->> rdf 12/04/2006