hypre/releases/checklist_general.txt

89 lines
2.1 KiB
Plaintext

** NOTE: This file still needs some work
HYPRE General Release Checklist
General releases occur infrequently. They are stable, well-documented and can
be downloaded from the HYPRE web site.
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: X.X.X
--->>
2. Copy this file to 'check{release number}.txt' and commit to the repository
--->>
3. Project personnel advised of release decision and tentative date with
a request to not disrupt the repository until the release is complete
--->>
4. Update user, reference, and developer manuals with information regarding
contents of this release
--->>
5. Initial documentation review meeting
--->>
6. Update CHANGELOG file with information regarding contents of this release
--->>
7. Final documentation review meeting
--->>
8. Verify that all agreed-upon changes have been committed
--->>
9. Project Lead review and/or concurrence to release
--->>
10. Update config/configure.in with release number and date, then run
config/bootstrap and commit changes to the repository
--->>
11. Tag repository with release number (use 'rtag -b' to create a branch)
--->>
12. Manually run the autotest script with the following options on the checked
out version: -tux149 -insure -gpsmp -pengra
--->>
13. If the test runs properly, proceed. Otherwise, untag the repository, make
necessary corrections, and return to step 10.
--->>
14. 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)
--->>
15. On the CASC cluster, copy tar file to /usr/casc/hypre
--->>
16. Put release on download page, and inform project team and other appropriate
users of availability
--->>
17. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository
--->>