Description of the procedure to release a new version
The following discussion from Manual-2.1!23 should be addressed:
-
@kraus started a discussion: (+1 comment)
A new version of the binary of Opal and in consequence of the manual as well. A few items that need to be done:
- increase the version string in CMakeLists.txt
- setup a repository for the new version of the manual
- setup the regression-tests to run the new version
- add links to the binaries in the wiki
- compile the change log and publish it in the wiki
- correct (the links to) the example input files, field maps aso in the manual
- write e-mail to mailing list
I guess there's a lot more to be done and as long as we don't write these steps down in a procedure that we follow we'll always have problems. We just had two e-mails from potential users of Opal that tried to run examples from the manual. Unfortunately they weren't updated when we released new versions.
\cc @gsell