anchor.diff:  +
   The last commit before the release has to have the `openscap-<version>` message (e.g. `openscap-1.2.17`).
   
  -6. Run `new-release.sh`.
  +. Run `new-release.sh`.
   +
   This will create and push version tags, create new GitHub release and handle milestones swap.
   Finally, it will bump version numbers in `versions.sh` to be ready for the next upstream release.
  
positive.code: +
  This changes the libtool library version number so it reflects the API/ABI change.
  
  5. Update the NEWS and make the release commit.
  +
  Make sure that everything in the repository is in place, and that the only thing missing is the `NEWS` file and tags.
  Use the `news_template.sh` script to generate a starting point for your `NEWS` file.
  
negative.code: 
  == Prerequisities ==
  
  * System with `python3.6` or greater, installed https://pypi.python.org/pypi/PyGithub/1.35[PyGithub] module.
  * A GitHub token - get one on https://github.com/settings/tokens. Choose `repo` scope.
  
  == Process ==
  
  . Clone a clean `openscap` repository:
  
     git clone https://github.com/OpenSCAP/openscap.git
  
  . Create `.env` file
  +
  You are supposed to define environment variables that contain sensitive information, s.a. GitHub access tokens.
  Create an `.env` file in the `release_tools` directory (i.e. where the release scripts are).
  Put your GitHub token in the `.env` file, so it contains the following line:
  
     GITHUB_TOKEN='<your token here>'
  
  . Check out that the information within `versions.sh` is accurate.
  +
  OpenSCAP versions are supposed to have correct values from the previous build (see the step 6), but e.g. the `latest_fedora` and `latest_rhel` may need to be updated if work on a distribution with new version has begun.
  
  . Run `up_to_compliance_check.sh`.
  +
  In the ideal case, the script ends after the ABI compatiblity check finishes.
  Review the check results and act accordingly to them.
  
  . Run `handle_ltversions.sh`.
  +
  According to the result from the compliance check (and the decision what to do about possible API/ABI changes), you run the script with an argument `bugfix`, `backwards_compatible` or `breaking_change`.
  +
  