diff options
| author | Lars Wirzenius <liw@liw.fi> | 2020-08-13 11:36:10 +0300 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2020-08-13 11:36:10 +0300 |
| commit | b6012c3a0146f966ebe807cac62f9b15e43fde33 (patch) | |
| tree | 849b3028ae3be177d21efcebeda18aa11d5196a4 | |
| parent | 16bd3726d9bc3ce7841e1628156a9fb945b01535 (diff) | |
| download | vmdb2.liw.fi-b6012c3a0146f966ebe807cac62f9b15e43fde33.tar.gz | |
doc: release proceess
| -rw-r--r-- | release.mdwn | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/release.mdwn b/release.mdwn new file mode 100644 index 0000000..39d97d4 --- /dev/null +++ b/release.mdwn @@ -0,0 +1,17 @@ +[[!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. |