New release.

releases/check2.3.1a.txt

@@ -0,0 +1,62 @@
+
+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.3.1a
+
+  [cht 1/31/2008]
+
+- Copy this file to 'check{release number}.txt'.
+
+  [cht 1/31/2008]
+
+- 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.
+
+  [cht 1/31/2008]
+
+- Update 'CHANGELOG' file with information regarding contents of this release.
+
+  [cht 1/31/2008]
+
+- Verify that all agreed-upon changes have been committed.
+
+  [cht 1/31/2008]
+
+- Project Lead review and/or concurrence to release.
+
+  [cht 1/31/2008]
+
+- Update 'config/configure.in' with release number and date, then run
+  'config/bootstrap' and commit changes to the repository.
+
+  [cht 1/31/2008]
+
+- Tag repository with release number.
+
+  [cht 2/1/2008]
+
+- Create release tar file 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.
+
+  [cht 2/1/2008]
+
+- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
+
+  [cht 2/1/2008]
+
+- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
+  this file to the repository.
+
+  [cht 2/1/2008]
+