anchor.diff:  * `bugfix`: No changes of API/ABI, the code got just some improvements under the hood.
   * `backwards_compatible`: API/ABI is backwards compatible - the API was expanded, new symbols were introduced.
   * `breaking_change`: API/ABI is not backwards compatible - the API was modified, symbols were removed, types have changed... If this happens, think about dropping symbols marked with openscap `OSCAP_DEPRECATED()` macro.
  +
   +
   This changes the libtool library version number so it reflects the API/ABI change.
   
  
positive.code: 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.
  Update the `AUTHORS` file for missing authors and the `naming.sh` file if there are duplicate author entries.
  
  Use it to update the `NEWS` file and commit it.
  +
  The last commit before the release has to have the `openscap-<version>` message (e.g. `openscap-1.2.17`).
  
negative.code: 6. 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.
  
  
  == To be done ==
  