vmdb2 → Release process

The release process is roughly as follows:

  • Make sure full Contractor tests pass, and fix any problems.
  • Create new branch.
    • Update NEWS to cover all changes since previous release
    • Update NEWS and vmdb/version.py with new version number, and commit.
    • Push to gitlab, merge.
    • Switch to master.
    • Pull down changes from gitlab.
  • Create signed tag vmdb2-x.y for new release x.y.
  • Update NEWS and vmdb/version.py with a version number for development, by appending "+git" to it, and commit.
  • Push tags to gitlab.
  • Push code and tags to git.liw.fi.
  • Announce on IRC (#vmdb2, alerting gwolf) and the fediverse and on the vmdb2.liw.fi site blog.