From 5caa49e945f4e079f2e62eb3a05c338696d3c875 Mon Sep 17 00:00:00 2001 From: Troy McConaghy Date: Wed, 14 Mar 2018 00:19:02 +0100 Subject: [PATCH] Add note at top how this is old, will be updated A more complete fix will have to be done later. This is what we can do for now. --- RELEASE_PROCESS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md index 776eecba..cb0e7642 100644 --- a/RELEASE_PROCESS.md +++ b/RELEASE_PROCESS.md @@ -1,5 +1,13 @@ # Our Release Process +## Notes + +This process hasn't been updated to the C4 way yet. That will simplify it a lot. Stay tuned! Until then, the basic idea is that there's only one branch: `master`. All releases are just Git tags of specific commits on the `master` branch. + +his is the _BigchainDB Server_ release process. The process to release other BigchainDB software will be similar but not identical. + +
+ The release process for BigchainDB server differs slightly depending on whether it's a minor or a patch release. BigchainDB follows