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: 2.2.0b

    --->> ab 9/18/07

 2. Copy this file to 'check{release number}.txt' and commit to the repository

    --->> ab 9/18/07

 3. Project personnel advised of release decision and tentative date with
    a request to not disrupt the repository until the release is complete

    --->> ab 9/18/07

 4. Update CHANGELOG file with information regarding contents of this release

    --->> ab 9/20/07

 5. Verify that user, reference, and developer manuals are updated

    --->> ab 9/20/07 (N/A for beta according to rdf) 

 6. Verify that all agreed-upon changes have been committed

    --->> ab 9/20/07

 7. Project Lead review and/or concurrence to release

    --->> ab 9/20/07

 8. Update config/configure.in with release number and date, then run
    config/bootstrap and commit changes to the repository

    --->> ab 9/20/07

 9. Tag repository with release number

    --->> ab 9/20/07 (cvs rtag V2-2-0b linear_solvers)

10. Manually run the autotest script with the following options on the checked
    out version: -tux149 -insure -gpsmp -pengra

    --->> ab 9/20/07 (N/A - relying on autotests from the previous week)

11. If the test runs properly, proceed.  Otherwise, untag the repository, make
    necessary corrections, and return to step 8.

    --->> N/A

12. 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)

    --->>  ab 9/20/07   (./tools/mkdist V2-2-0b)

13. On the CASC cluster, copy tar file to /usr/casc/hypre

    --->> ab 9/20/07

14. Put release on download page, and inform project team and other appropriate
    users of availability

    --->> rdf 10/3/2007 (never sent a release email to users)

15. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
    this file to the repository

    --->> rdf 1/24/2008