summaryrefslogtreecommitdiff
path: root/release.mdwn
blob: 451c7e10cf20388d64e5c0da5dcc873c8079caa0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[[!meta title="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.