dev:release_checklist
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:release_checklist [2017/10/23 16:04] – Add missing cd 129.129.214.74 | dev:release_checklist [2019/12/05 14:29] – adapt to new Git workflow (still WiP) tmueller | ||
---|---|---|---|
Line 5: | Line 5: | ||
* a) Clean status for all dashboard regression testers | * a) Clean status for all dashboard regression testers | ||
* b) Successful build and clean regtest of the gfortran sdbg, sopt, popt, pdbg, ssmp, and psmp versions | * b) Successful build and clean regtest of the gfortran sdbg, sopt, popt, pdbg, ssmp, and psmp versions | ||
- | * c) Check the SMP executables with H2O-32 benchmark input, e.g. using the script | + | * c) Check the generated |
- | < | + | < |
- | #!/bin/sh | + | cd cp2k/benchmarks/QS |
- | cwd=$PWD | + | ./check-release-comparison.py |
- | cd cp2k/tests/QS/ | + | |
- | # | + | |
- | ../../ | + | |
- | export OMP_NUM_THREADS=1 | + | |
- | mpiexec -np 8 ../ | + | |
- | # | + | |
- | ../ | + | |
- | export OMP_NUM_THREADS=1 | + | |
- | mpiexec -np 8 ../ | + | |
- | # | + | |
- | ../ | + | |
- | export OMP_NUM_THREADS=2 | + | |
- | mpiexec -np 4 ../ | + | |
- | # | + | |
- | ../ | + | |
- | export OMP_NUM_THREADS=4 | + | |
- | mpiexec -np 2 ../ | + | |
- | # | + | |
- | ../ | + | |
- | export OMP_NUM_THREADS=8 | + | |
- | mpiexec -np 1 ../ | + | |
- | # | + | |
- | ../ | + | |
- | export OMP_NUM_THREADS=8 | + | |
- | ../ | + | |
- | # | + | |
- | cd ${cwd} | + | |
- | # | + | |
- | for f in H2O-32-*.out; | + | |
</ | </ | ||
+ | |||
The final energies of all MD runs should agree by 10< | The final energies of all MD runs should agree by 10< | ||
- | === 3. Create a new branch | + | === 3. Create a new branch |
< | < | ||
- | svn mkdir svn+ssh://mkrack@svn.code.sf.net/ | + | git checkout -b support/vX.Y |
</ | </ | ||
- | Description text: " | ||
- | === 4. Copy the current CP2K version from the trunk using === | + | === 4. Apply release specific changes === |
- | < | + | |
- | svn copy -m " | + | * a) Update the version in src/cp2k_info.F (comment/ |
- | svn+ssh:// | + | * b) Update the version in tools/ |
- | svn+ssh:// | + | * c) Provide Java version of [[http:// |
- | </ | + | * d) Create a file cp2k/ |
- | === 5. Check the release version out using === | + | |
- | < | + | |
- | svn co svn+ssh:// | + | |
- | </ | + | |
- | === 6. Apply release specific changes === | + | |
- | * a) Change | + | |
- | * b) Provide Java version of [[http:// | + | |
- | * c) Create a file cp2k/ | + | |
< | < | ||
- | cd cp2k-X_Y-branch/ | + | tools/ |
- | tools/ | + | git add REVISION |
- | svn add REVISION | + | git commit |
- | svn ci -m "Store the revision number of the release branch" | + | |
- | cd .. | + | |
</ | </ | ||
- | === 7. Compile the release branch version and run one or more regression tests === | + | === 5. Compile the release branch version and run one or more regression tests === |
The reference outputs can be retrieved from the branched CP2K trunk version: | The reference outputs can be retrieved from the branched CP2K trunk version: | ||
< | < | ||
Line 79: | Line 43: | ||
</ | </ | ||
- | === 8. Create a new manual on " | + | === 6. Create a new manual on " |
- | * a) Login to " | + | |
- | * b) Create a new folder '' | + | |
- | * c) Add a new link in the index.html file and logout | + | |
- | * d) Update index file | + | |
- | * e) Create and upload the new manual: | + | |
- | < | + | |
- | cd cp2k/ | + | |
- | ./ | + | |
- | </ | + | |
- | === 9. Export the release branch | + | * a) Login to "sham.cp2k.org" |
- | < | + | * b) Create a new folder '' |
- | svn export http://svn.code.sf.net/ | + | * c) Add a new link in the cp2k/ |
- | </ | + | * d) Create and upload the new manual: |
- | === 10. Create a bzip2 tar file using === | ||
< | < | ||
- | tar -cjf cp2k-X.Y.tar.bz2 cp2k-X.Y | + | cd cp2k/ |
+ | ./ | ||
</ | </ | ||
- | === 11. Check the exported branch | + | === 7. Tag the release and push both tag and branch to GitHub |
- | Create statically linked '' | + | |
- | < | + | |
- | ln -s cp2k-X.Y cp2k | + | |
- | cd cp2k/ | + | |
- | make -j ARCH=Linux-x86-64-gfortran VERSION=ssmp | + | |
- | make -j ARCH=Linux-x86-64-gfortran VERSION=sopt | + | |
- | cd ../.. | + | |
- | </ | + | |
- | === 12. Upload the tar files to sourceforge to make it appear in the list under " | ||
< | < | ||
- | scp cp2k-X.Y/ | + | git tag -a -m "CP2K release |
- | scp cp2k-X.Y/ | + | git push --atomic upstream vX.Y.0 support/vX.Y |
- | scp cp2k-X.Y.tar.bz2 mkrack@frs.sourceforge.net:/home/ | + | |
</ | </ | ||
- | === 13. Increment the version number of the development version | + | === 8. Increment the version number of the development version (skip this for sub-releases) === |
< | < | ||
- | cp2k/ | + | git checkout master |
- | cp2k/ | + | vim cp2k/ |
- | cd cp2k | + | git commit |
- | svn ci -m " | + | |
</ | </ | ||
- | === 14. Update the CP2K web page === | + | === 9. Update the CP2K web page === |
* Add [[: | * Add [[: | ||
* Update [[: | * Update [[: | ||
- | === 15. Dissemination === | + | === 10. Dissemination === |
Inform the | Inform the | ||
+ | |||
* CP2K developers by email | * CP2K developers by email | ||
* CP2K users via the CP2K mailing list | * CP2K users via the CP2K mailing list | ||
+ | * the Twitter-sphere via the Twitter account | ||
+ | |||
about the new CP2K release. | about the new CP2K release. | ||
- | For a new sub-release X.Y repeat | + | For a new sub-release X.Y repeat |
dev/release_checklist.txt · Last modified: 2024/05/05 19:43 by oschuett