From b6012c3a0146f966ebe807cac62f9b15e43fde33 Mon Sep 17 00:00:00 2001
From: Lars Wirzenius <liw@liw.fi>
Date: Thu, 13 Aug 2020 11:36:10 +0300
Subject: doc: release proceess

---
 release.mdwn | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 release.mdwn

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.
-- 
cgit v1.2.1