Release 2.1.12

[jcvenegas]

Change release process, instead create a release candidate we can test the HEAD what will be the last commit using new autoamted obs package generation we can generate and test commits based on HEAD.

• Test the HEAD commit of the master branch using the tests included in the source code within the tests/ directory.
• Run Coverity Scan on HEAD commit and ensure no medium or high severity issues are reported.
• Update versions.txt with package versions used by the release and the cc-oci-runtime.
• Generate OBS packages based on HEAD.
• Test OBS packages
  • Manual tests
    • Installation test.
    • Package signature test.
  • Automated tests
    • Integration tests included in the source code under the tests/integration directory.
• Update configure.ac with the cc-oci-runtime version tagged.
• Tag release using new version.
• Write release notes:
  • Brief summary of known issues, pointing to the appropriate Issues/PRs.
  • Version of Docker (ideally range of versions, or "up to version X") supported by the release.
  • Version of the OCI spec (ideally range of versions, or "up to version X") supported by the release.
  • Version of Clear Container image used by the release.
  • Add links to Installation instructions.
  • Document any common vulnerabilities and exposures (CVEs) fixed with links to the CVE database.
• Post release details on the public mailing list.
• Update public IRC channel with a link to the latest release.