CFD/hypre
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Release 2.10.1 is done except for the web page. Changed some scripts and a few other things

Browse Source 
related to the new versioning system.
This commit is contained in:
Rob Falgout 2015-09-11 14:31:44 -07:00
parent 8b2efbf182
commit fc2682dd6d
8 changed files with 118 additions and 407 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
AUTOTEST/testdist.sh
View File

@ -12,9 +12,9 @@
#EHEADER**********************************************************************
# Which tests to run?
TEST_ALPHA="-tux339"
TEST_BETA="$TEST_ALPHA -rzzeus -rzmerl -vulcan"
TEST_GENERAL="$TEST_BETA"
TEST_PATCH="-tux339"
TEST_MINOR="$TEST_PATCH -rzzeus -rzmerl -vulcan"
TEST_MAJOR="$TEST_MINOR"
TERMCMD=""
while [ "$*" ]
@ -33,13 +33,13 @@ do
-t|-trace echo each command
This script unpacks {release} in the parent directory and lists the tests
needed to verify it. The list depends on the release type (alpha, beta, or
general). If all required tests have passed, the script will generate a
verification file containing the logs from the runs. Otherwise, tests that
have failed or have not been run yet can be started, and the script will
have to be re-run after their completion to generate the verification file.
needed to verify it, based on the type of release (MAJOR, MINOR, or PATCH).
If all required tests pass, a verification file is generated containing the
logs from the runs. Otherwise, tests that have failed or have not been run
yet can be started, and the script will have to be re-run after their
completion to generate the verification file.
Example usage: $0 /usr/casc/hypre/hypre-2.0.0.tar.gz
Example usage: $0 /usr/casc/hypre/hypre-2.10.1.tar.gz
NOTE: The absolute path for the release is required.
@ -75,10 +75,10 @@ release_dir=`basename $release_file | awk -F.tar '{print $1}'`
release=`echo $release_dir | sed 's/hypre-//' | sed 's/.tar.gz//'`
output_dir="$testing_dir/AUTOTEST-hypre-$release"
case $release in
*[0-9].*[0-9].*[0-9]) NAME="GENERAL"; TESTS=$TEST_GENERAL ;;
*[0-9].*[0-9].*[0-9]b) NAME="BETA"; TESTS=$TEST_BETA ;;
*[0-9].*[0-9].*[0-9]a) NAME="ALPHA"; TESTS=$TEST_ALPHA ;;
*) NAME="ALPHA"; TESTS=$TEST_ALPHA ;;
[1-9][0-9]*.0.0) NAME="MAJOR"; TESTS=$TEST_MAJOR ;;
[1-9][0-9]*.[1-9][0-9]*.0) NAME="MINOR"; TESTS=$TEST_MINOR ;;
[1-9][0-9]*.[1-9][0-9]*.[1-9][0-9]*) NAME="PATCH"; TESTS=$TEST_PATCH ;;
*) NAME="PATCH"; TESTS=$TEST_PATCH ;;
esac
# Extract the release

BIN
releases/AUTOTEST-hypre-2.10.1.tgz Normal file
View File

Binary file not shown.

119
releases/check2.10.1.txt
View File

@ -1,96 +1,79 @@
HYPRE Release Checklist
Releases are given a number of the form MAJOR.MINOR.PATCH, where an increment in
one of the digits denotes the following (in general):
Releases are assigned a number of the form MAJOR.MINOR.PATCH, where an increment
in one of the digits denotes the following (in general):
MAJOR - backward incompatible release (API changes)
MINOR - new features
PATCH - bug fixes or other trivial changes
The steps below must be completed (as indicated) and initialed/dated on the []
line by the responsible project member before the release is made available.
See the Developer's Manual for more information on creating new releases.
The following steps must be completed, initialed and dated on the [] line by the
responsible project member before the release is made available to users. Some
of the steps are optional for PATCH and MINOR releases (as indicated below).
================================================================================
[rdf 5/1/2015] MAJOR.MINOR.PATCH
Decision made for release number 2.10.1
- Decision made for release number 2.10.1
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Copy this file to 'check{release number}.txt'.
[rdf 5/1/2015] MAJOR.MINOR.PATCH
[rdf 5/1/2015] MAJOR.MINOR.PATCH
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.
- Copy this file to 'check{release number}.txt'.
[skip] MAJOR
Initial documentation review meeting.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
[skip] MAJOR.MINOR
Update user, reference, and developer manuals with information regarding
contents of this release.
- 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.
[skip] MAJOR
Final documentation review meeting.
[rdf 5/1/2015] MAJOR.MINOR.PATCH
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Update 'CHANGELOG' file with information regarding contents of this release.
- Initial documentation review meeting.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Verify that all agreed-upon changes have been committed.
[] MAJOR
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
- Update user, reference, and developer manuals with information regarding
contents of this release.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR
[rdf 9/11/2015] MAJOR.MINOR.PATCH
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.
- Final documentation review meeting.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
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.
[] MAJOR
[rdf 9/11/2015] MAJOR.MINOR.PATCH
Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
- Update 'CHANGELOG' file with information regarding contents of this release.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
[rdf 9/11/2015] MAJOR.MINOR.PATCH
On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
- Verify that all agreed-upon changes have been committed.
[] MAJOR.MINOR.PATCH
Put release on download page, and inform project team and other appropriate
users of availability.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
[] MAJOR.MINOR.PATCH
FINAL CERTIFICATION: Verify that all steps have been signed off and commit this
file to the repository.
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
- Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR.PATCH
- 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.
[] MAJOR.MINOR.PATCH
- 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.
[] MAJOR.MINOR.PATCH
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[] MAJOR.MINOR.PATCH
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[] MAJOR.MINOR.PATCH
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[] MAJOR.MINOR.PATCH
- Put release on download page, and inform project team and other appropriate
users of availability.
[] MAJOR.MINOR.PATCH
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[] MAJOR.MINOR.PATCH

119
releases/checklist.txt
View File

@ -1,96 +1,79 @@
HYPRE Release Checklist
Releases are given a number of the form MAJOR.MINOR.PATCH, where an increment in
one of the digits denotes the following (in general):
Releases are assigned a number of the form MAJOR.MINOR.PATCH, where an increment
in one of the digits denotes the following (in general):
MAJOR - backward incompatible release (API changes)
MINOR - new features
PATCH - bug fixes or other trivial changes
The steps below must be completed (as indicated) and initialed/dated on the []
line by the responsible project member before the release is made available.
See the Developer's Manual for more information on creating new releases.
The following steps must be completed, initialed and dated on the [] line by the
responsible project member before the release is made available to users. Some
of the steps are optional for PATCH and MINOR releases (as indicated below).
================================================================================
[fml m/d/yyyy] MAJOR.MINOR.PATCH
Decision made for release number X.X.X
- Decision made for release number X.X.X
[] MAJOR.MINOR.PATCH
Copy this file to 'check{release number}.txt'.
[fml m/d/yyyy] MAJOR.MINOR.PATCH
[] MAJOR.MINOR.PATCH
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.
- Copy this file to 'check{release number}.txt'.
[] MAJOR
Initial documentation review meeting.
[] MAJOR.MINOR.PATCH
[] MAJOR.MINOR
Update user, reference, and developer manuals with information regarding
contents of this release.
- 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.
[] MAJOR
Final documentation review meeting.
[] MAJOR.MINOR.PATCH
[] MAJOR.MINOR.PATCH
Update 'CHANGELOG' file with information regarding contents of this release.
- Initial documentation review meeting.
[] MAJOR.MINOR.PATCH
Verify that all agreed-upon changes have been committed.
[] MAJOR
[] MAJOR.MINOR.PATCH
Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
- Update user, reference, and developer manuals with information regarding
contents of this release.
[] MAJOR.MINOR.PATCH
Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR
[] MAJOR.MINOR.PATCH
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.
- Final documentation review meeting.
[] MAJOR.MINOR.PATCH
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.
[] MAJOR
[] MAJOR.MINOR.PATCH
Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
- Update 'CHANGELOG' file with information regarding contents of this release.
[] MAJOR.MINOR.PATCH
On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[] MAJOR.MINOR.PATCH
[] MAJOR.MINOR.PATCH
On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
- Verify that all agreed-upon changes have been committed.
[] MAJOR.MINOR.PATCH
Put release on download page, and inform project team and other appropriate
users of availability.
[] MAJOR.MINOR.PATCH
[] MAJOR.MINOR.PATCH
FINAL CERTIFICATION: Verify that all steps have been signed off and commit this
file to the repository.
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[] MAJOR.MINOR.PATCH
- Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR.PATCH
- 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.
[] MAJOR.MINOR.PATCH
- 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.
[] MAJOR.MINOR.PATCH
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[] MAJOR.MINOR.PATCH
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[] MAJOR.MINOR.PATCH
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[] MAJOR.MINOR.PATCH
- Put release on download page, and inform project team and other appropriate
users of availability.
[] MAJOR.MINOR.PATCH
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[] MAJOR.MINOR.PATCH

73
releases/checklist_alpha.txt
View File

@ -1,73 +0,0 @@
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 X.X.Xa
[fml m/d/yyyy]
- Copy this file to 'check{release number}.txt'.
[]
- 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.
[]
- Update 'CHANGELOG' file with information regarding contents of this release.
[]
- Verify that all agreed-upon changes have been committed.
[]
- Project Lead review and/or concurrence to release.
[]
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[]
- Tag repository with release number: git tag -a V2-8-2a -m "Release 2.8.2a".
Push the tags to the central repository: git push --tags
[]
- 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.
[]
- 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.
[**OPTIONAL**]
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[**OPTIONAL**]
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[]
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[]

87
releases/checklist_beta.txt
View File

@ -1,87 +0,0 @@
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 X.X.Xb
[fml m/d/yyyy]
- Copy this file to 'check{release number}.txt'.
[]
- 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.
[]
- Update user, reference, and developer manuals with information regarding
contents of this release.
[]
- Update 'CHANGELOG' file with information regarding contents of this release.
[]
- Verify that all agreed-upon changes have been committed.
[]
- Project Lead review and/or concurrence to release.
[]
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[]
- Tag repository with release number: git tag -a V2-8-0b -m "Release 2.8.0b".
Push the tags to the central repository: git push --tags
[]
- 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.
[]
- 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.
[]
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[]
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[]
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[]
- Put release on download page, and inform project team and other appropriate
users of availability.
[]
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[]

95
releases/checklist_general.txt
View File

@ -1,95 +0,0 @@
HYPRE General Release Checklist
General releases occur infrequently. They are stable, well-documented and can
be downloaded from the HYPRE web site.
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 X.X.X
[fml m/d/yyyy]
- Copy this file to 'check{release number}.txt'.
[]
- 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.
[]
- Initial documentation review meeting.
[]
- Update user, reference, and developer manuals with information regarding
contents of this release.
[]
- Final documentation review meeting.
[]
- Update 'CHANGELOG' file with information regarding contents of this release.
[]
- Verify that all agreed-upon changes have been committed.
[]
- Project Lead review and/or concurrence to release.
[]
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[]
- Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[]
- 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.
[]
- 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.
[]
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[]
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[]
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[]
- Put release on download page, and inform project team and other appropriate
users of availability.
[]
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[]

6
tools/mkdist
View File

@ -32,8 +32,8 @@ help ()
VersionId Creates a distribution, where VersionId determines the
repository revision to use. VersionId can either have the
form VM-m-r to specify a release tag or Dyyyy-mm-dd to
specify a date. For example, V2-5-0a checks out source with
tag 'V2-5-0a' and creates the tar file hypre-2.5.0a.tar.gz.
specify a date. For example, V2-10-1 checks out source with
tag 'V2-10-1' and creates the tar file hypre-2.10.1.tar.gz.
The option D2010-01-27 checks out the most recent source not
later than the date '2010-01-27' and creates the tar file
hypre-2010.01.27.tar.gz. The V option is used to create
@ -41,7 +41,7 @@ help ()
temporary releases for colleagues.
Example usage: $0 -display
$0 V2-5-0a
$0 V2-10-1
$0 D2010-01-27
EOF