hypre/releases/check2.8.0b.txt
2011-11-15 21:30:07 +00:00

83 lines
2.2 KiB
Plaintext

HYPRE Beta Release Checklist
Beta releases tend to occur somewhat frequently. They may include new
technology, but they are reasonably stable.
See the Developer's Manual for more information on creating new releases.
The following steps must be completed, initialed & dated on the [] line by
the responsible project member before the release is made available to users.
- Decision made for release number 2.8.0b
[rdf 11/14/2011]
- Copy this file to 'check{release number}.txt'.
[rdf 11/14/2011]
- Create a tracker issue "New hypre release {number}" advising project personnel
of release decision and tentative date with a request to not disrupt the
repository until the release is complete.
[rdf 11/14/2011]
- Update user, reference, and developer manuals with information regarding
contents of this release.
[rdf 11/14/2011]
- Update 'CHANGELOG' file with information regarding contents of this release.
[rdf 11/14/2011]
- Verify that all agreed-upon changes have been committed.
[rdf 11/14/2011]
- Project Lead review and/or concurrence to release.
[rdf 11/14/2011]
- Update 'config/configure.in' with release number and date, then run
'config/bootstrap' and commit changes to the repository.
[rdf 11/14/2011]
- Tag repository with release number.
[rdf 11/14/2011]
- Create release tar files by running the 'tools/mkdist' script (for more
information, do 'mkdist -help'). This can be run from within any directory,
just be sure to use the latest version of the 'mkdist' script.
[rdf 11/14/2011]
- Run the 'AUTOTEST/testdist.sh' script to verify a stable release. For more
information on running this script, do 'testdist.sh -help'. If any of the
tests fail, untag the repository, make necessary corrections, and start over.
[rdf 11/15/2011]
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[rdf 11/15/2011]
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[rdf 11/15/2011]
- Put release on download page, and inform project team and other appropriate
users of availability.
[rdf 11/15/2011]
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[rdf 11/15/2011]