Release Guide

This helps me to prevent mistakes when releasing new versions.

Release:

1. Check whether we need to update doc/user_manual.adoc with new text or screenshots, depends on what changed in the version
2. cd build; make cppcheck; cat cppcheck.txt - review the cppcheck output for issues that are horrible = release blockers or easy to fix - we can fix them before the release quickly
3. Check version in CMakeLists.txt - SCAP_WORKBENCH_VERSION_*
4. git tag; git push --tags
5. cd build; make package_source
6. make sure the tarball contains doc/user_manual.html
7. Create Release draft in GitHub and upload the tarball
8. Update the webpage (section tools->redirections)
9. Upload new manual (build static_openscap_docs in Jenkins)
10. Update the openscap portal version redirects (Dashboard -> Tools -> Redirection)

GitHub issues:

1. Mark the appropriate milestone as finished
2. Make sure there is another milestone for the next version and that it is the default milestone

Mailing list:

1. announce it on the open-scap mailing list

Fedora:

1. Build for rawhide
2. Build and push bodhi updates

COPR:

1. Build for COPR repo: https://copr.fedorainfracloud.org/coprs/openscapmaint/openscap-latest/builds/

Version bump:

1. CMakeLists.txt - SCAP_WORKBENCH_VERSION_*