Checking in initial file for 2.1.0a release.

releases/check2.1.0a.txt

@@ -0,0 +1,53 @@
+
+HYPRE Alpha Release Checklist
+
+Alpha releases are primarily used to get new code to collaborators quickly.
+These releases may not be 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.1.0a
+
+    --->> tk 06/21/07
+
+ 2. Copy this file to 'check{release number}.txt' and commit to the repository
+
+    --->> tk 06/25/07
+
+ 4. Update CHANGELOG file with information regarding contents of this release
+
+    --->> tk 06/25/07
+
+ 5. Verify that all agreed-upon changes have been committed
+
+    --->> tk 06/25/07
+
+ 6. Project Lead review and/or concurrence to release
+
+    --->> rdf 06/25/07
+
+ 7. Update config/configure.in with release number and date, then run
+    config/bootstrap and commit changes to the repository
+
+    --->> 
+
+ 8. Tag repository with release number
+
+    --->> 
+
+ 9. 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)
+
+    --->> 
+
+10. On the CASC cluster, copy tar file to /usr/casc/hypre
+
+    --->> 
+
+11. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
+    this file to the repository
+
+    --->>