dev:release_checklist
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| dev:release_checklist [2018/06/12 13:40] – Add sdbg 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 |
| + | |||
| + | * a) Update the version in src/ | ||
| + | * b) Update the version in tools/ | ||
| + | * c) Provide Java version of [[http:// | ||
| + | * d) Create a file cp2k/ | ||
| < | < | ||
| - | svn copy -m " | + | tools/ |
| - | svn+ssh:// | + | git add REVISION |
| - | svn+ssh:// | + | git commit |
| - | </ | + | |
| - | === 5. Check the release version out using === | + | |
| - | < | + | |
| - | svn co svn+ssh:// | + | |
| - | </ | + | |
| - | === 6. Apply release specific changes === | + | |
| - | * a) Change cp2k_info.F (comment/ | + | |
| - | * b) Provide Java version of [[http:// | + | |
| - | * c) Create a file cp2k/ | + | |
| - | < | + | |
| - | cd cp2k-X_Y-branch/ | + | |
| - | tools/ | + | |
| - | svn add REVISION | + | |
| - | 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 " | * a) Login to " | ||
| * b) Create a new folder ''/ | * b) Create a new folder ''/ | ||
| * c) Add a new link in the cp2k/ | * c) Add a new link in the cp2k/ | ||
| * d) Create and upload the new manual: | * d) Create and upload the new manual: | ||
| + | |||
| < | < | ||
| cd cp2k/ | cd cp2k/ | ||
| - | ./ | + | ./ |
| </ | </ | ||
| - | === 9. Export | + | === 7. Tag the release |
| - | < | + | |
| - | svn export http:// | + | |
| - | </ | + | |
| - | === 10. Create a bzip2 tar file using === | ||
| < | < | ||
| - | tar -cjf cp2k-X.Y.tar.bz2 cp2k-X.Y | + | git tag -a -m "CP2K release |
| + | git push --atomic upstream vX.Y.0 support/vX.Y | ||
| </ | </ | ||
| - | === 11. Check the exported branch release | + | === 8. Increment |
| - | Create statically linked '' | + | |
| < | < | ||
| - | ln -s cp2k-X.Y cp2k | + | git checkout master |
| - | cd cp2k/makefiles | + | vim cp2k/ |
| - | make -j ARCH=Linux-x86-64-gfortran VERSION=ssmp | + | git commit - " |
| - | make -j ARCH=Linux-x86-64-gfortran VERSION=sopt | + | |
| - | make -j ARCH=Linux-x86-64-gfortran VERSION=sdbg | + | |
| - | cd ../.. | + | |
| </ | </ | ||
| - | === 12. Upload | + | === 9. Update |
| - | < | + | |
| - | scp cp2k-X.Y/ | + | |
| - | scp cp2k-X.Y/ | + | |
| - | scp cp2k-X.Y/ | + | |
| - | scp cp2k-X.Y.tar.bz2 mkrack@frs.sourceforge.net:/ | + | |
| - | </ | + | |
| - | + | ||
| - | === 13. Increment the version number of the development version in the files (skip this for sub-releases) === | + | |
| - | < | + | |
| - | cp2k/ | + | |
| - | cp2k/ | + | |
| - | cd cp2k | + | |
| - | svn ci -m " | + | |
| - | </ | + | |
| - | + | ||
| - | === 14. Create a git tag and push it to github | + | |
| - | === 15. Update the CP2K web page === | ||
| * Add [[: | * Add [[: | ||
| * Update [[: | * Update [[: | ||
| - | === 16. 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/01/01 23:40 by oschuett