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

Updating.

Browse Source
This commit is contained in:
falgout 2006-12-01 00:35:42 +00:00
parent 5bd53deacb
commit 6dffaf5a44
5 changed files with 154 additions and 266 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
releases/checklist_alpha.txt Normal file
View File

@ -0,0 +1,57 @@
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: X.X.Xa
--->>
2. Copy this file to 'check{release number}.txt' and commit to the repository
--->>
4. Update CHANGELOG file with information regarding contents of this release
--->>
5. Verify that all agreed-upon changes have been committed
--->>
6. Project Lead review and/or concurrence to release
--->>
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. Checkout tagged version
--->>
10. 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)
--->>
11. On the CASC cluster, copy tar file to /usr/casc/hypre
--->>
12. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository
--->>

102
releases/checklist_alpha_release
View File

@ -1,102 +0,0 @@
HYPRE Alpha Release Checklist
Alpha releases are primarily used to get new code to close collaborators quickly.
These releases tend to occur frequently, are available only on the CASC cluster
and 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
--->> _________________________________________
2. Release number:
--->> _________________________________________
3. Copy file checklist_alpha_release to check{verson number}.txt (i.e. check1.9.0a.txt)
and commit to the linear_solvers/releases directory
--->> _________________________________________
4. Project personnel advised of release decision and tentative date with
a request to not disrupt the repository until the release is complete
--->> _________________________________________
5. Requests for delay in release must be made within 24 hours of notification
--->> _________________________________________
6. Update CHANGELOG file with information regarding contents of this release
--->> _________________________________________
7. Project Lead review and/or concurrence to release
--->> _________________________________________
8. Update config/configure.in with release number and date; run
./config/bootstrap and commit changes to repository
--->> _________________________________________
9. Tag repository with release number (i.e. cvs rtag VM-mm-ra linear_solvers)
--->> _________________________________________
10. Checkout tagged version
--->> _________________________________________
11. Create tar file of checked out version by running the mkdist script
./mkdist [VersionID] (run in local directory above linear_solvers)
--->> _________________________________________
12. Manually untar the file that was created in step 11
--->> _________________________________________
13. Manually run the autotest script with the -tux149 and -insure options on
the checked out version
--->> _________________________________________
14. If the test runs properly, proceed to step 15
Otherwise, untag the repository, make necessary corrections, return
to step 9; iterating until all tests run correctly.
--->> _________________________________________
15. Copy tar file to /usr/casc/hypre directory
--->> _________________________________________
16. Run the mkdistlinks script to create symbolic links to the tar file
./mkdistlinks <HypreArchiveFileName>
--->> _________________________________________
17. cd to i686-pc-linux-gnu sub-directory
--->> _________________________________________
18. Run the mklibs script with the '-a install' option to create
and install the release
../mklibs -a <HypreArchiveFileName> install
--->> _________________________________________
19. If there are no errors in steps 11-18; inform project team and other
appropriate users of availability
--->> _________________________________________
20. FINAL SIGN-OFF
Verify that all steps have been signed off and commit this file to
the repository
--->> _________________________________________

2
releases/checklist_beta.txt
View File

@ -8,7 +8,7 @@ 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: X.X.X
1. Decision made for release number: X.X.Xb
--->>

96
releases/checklist_general.txt Normal file
View File

@ -0,0 +1,96 @@
** NOTE: This file still needs some work
HYPRE General Release Checklist
General releases occur infrequently. They are stable, well-documented and can
be downloaded from the HYPRE web site.
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: X.X.X
--->>
2. Copy this file to 'check{release number}.txt' and commit to the repository
--->>
3. Project personnel advised 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
--->>
*. Initial documentation review meeting
--->>
4. Update CHANGELOG file with information regarding contents of this release
--->>
*. Create beta release
--->>
*. Final documentation review meeting
--->>
6. Verify that all agreed-upon changes have been committed
--->>
7. Project Lead review and/or concurrence to release
--->>
8. Update config/configure.in with release number and date, then run
config/bootstrap and commit changes to the repository
--->>
9. Tag repository with release number
--->>
10. Checkout tagged version
--->>
11. Manually run the autotest script with the following options on the checked
out version: -tux149 -insure -gpsmp -pengra
--->>
12. If the test runs properly, proceed. Otherwise, untag the repository, make
necessary corrections, and return to step 8.
--->>
13. 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)
--->>
14. On the CASC cluster, copy tar file to /usr/casc/hypre
--->>
15. Put release on download page, and inform project team and other appropriate
users of availability
--->>
16. FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository
--->>

163
releases/checklist_general_release
View File

@ -1,163 +0,0 @@
HYPRE General Release Checklist
General releases occur infrequently. They are stable, well-documented and can
be downloaded from the HYPRE web site. 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
--->> _________________________________________
2. Release number:
--->> _________________________________________
3. Copy file checklist_general_release to check{release number}.txt (i.e. check1.9.0.txt)
and commit to the linear_solvers/releases directory
--->> _________________________________________
4. Project personnel advised of release decision and tentative date with
a request for no new code to be checked into the repository until
the release is complete
--->> _________________________________________
5. Requests for delay in release must be made within 24 hours of notification
--->> _________________________________________
6. Update user, reference and developer manuals with information regarding
contents of this release
--->> _________________________________________
7. Update CHANGELOG file with information regarding contents of this release
--->> _________________________________________
8. Initial documentation review meeting
--->> _________________________________________
9. Project Lead review and/or concurrence to release
--->> _________________________________________
10. Create beta release and install; if not already done
--->> _________________________________________
11. Final documentation review meeting
--->> _________________________________________
12. Verify all agreed upon changes, especially documentation, have been committed
--->> _________________________________________
13. Project Lead review and/or concurrence to release
--->> _________________________________________
14. Update config/configure.in with release number and date; run
./config/bootstrap and commit changes to repository
--->> _________________________________________
15. Create a repository tag with branch option for the release number
--->> _________________________________________
16. Checkout tagged version
--->> _________________________________________
17. Create tar file of checked out version by running the mkdist script
./mkdist [VersionId] (run in local directory above linear_solvers)
--->> _________________________________________
18. Manually untar the file that was created in step 16
--->> _________________________________________
19. Manually run the autotest script with the following options on the checked
out version: -tux149 -insure -gpsmp -pengra
--->> _________________________________________
20. If the tests run properly, proceed to step 20
Otherwise, untag the repository, make necessary corrections, return
to step 14; iterating until all tests run correctly.
--->> _________________________________________
21. Copy tar file to any closed (SCF) computer system, using FIS
--->> _________________________________________
22. On the CASC cluster, copy tar file to /usr/casc/hypre/i686-pc-linux-gnu directory
--->> _________________________________________
23. Run the mkdistlinks script to create symbolic links to the tar file
./mkdistlinks <HypreArchiveFileName>
(run in /usr/casc/hypre and OCF directory /usr/gapps/hypre)
--->> _________________________________________
24. On each OCF SYS_TYPE platform, including the CASC cluster, run the mklibs
script in the /usr/casc/hypre and/or /usr/gapps/hypre directories to
create and install the release
./mklibs -g <HypreArchiveFileName> install
--->> _________________________________________
25. Log onto any closed (SCF) computer system
--->> _________________________________________
26. Retrieve the tar file from the FIS system
--->> _________________________________________
27. Manually untar the file that was retrieved in step 25
--->> _________________________________________
28. Manually run the autotest script with the following options on the checked
out version: -sc -lilac
--->> _________________________________________
29. Copy tar file to the appropriate sub-directory (based on SYS_TYPE) of
/usr/gapps/hypre
--->> _________________________________________
30. Run the mkdistlinks script to create symbolic links to the tar file
./mkdistlinks <HypreArchiveFileName>
(run in /usr/gapps/hypre)
--->> _________________________________________
31. On each SCF SYS_TYPE platform run the mklibs script in the /usr/gapps/hypre
directory to create and install the release
./mklibs -g <HypreArchiveFileName> install
--->> _________________________________________
32. If there are no errors in steps 16-30; inform project team and other
appropriate users of availability
--->> _________________________________________
33. FINAL SIGN-OFF
Verify that all steps have been signed off and commit this file to
the repository
--->> _________________________________________