62 lines
1.6 KiB
Plaintext
62 lines
1.6 KiB
Plaintext
|
|
HYPRE Alpha Release Checklist
|
|
|
|
Alpha releases are primarily used to get new code to collaborators quickly.
|
|
These releases may not be 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.7.1a
|
|
|
|
[rdf 3/17/2011]
|
|
|
|
- Copy this file to 'check{release number}.txt'.
|
|
|
|
[rdf 3/17/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 3/17/2011]
|
|
|
|
- Update 'CHANGELOG' file with information regarding contents of this release.
|
|
|
|
[rdf 3/17/2011]
|
|
|
|
- Verify that all agreed-upon changes have been committed.
|
|
|
|
[rdf 3/17/2011]
|
|
|
|
- Project Lead review and/or concurrence to release.
|
|
|
|
[rdf 3/17/2011]
|
|
|
|
- Update 'config/configure.in' with release number and date, then run
|
|
'config/bootstrap' and commit changes to the repository.
|
|
|
|
[rdf 3/18/2011]
|
|
|
|
- Tag repository with release number.
|
|
|
|
[rdf 3/18/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 3/18/2011]
|
|
|
|
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
|
|
|
|
[rdf 3/18/2011]
|
|
|
|
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
|
|
this file to the repository.
|
|
|
|
[rdf 3/18/2011]
|