Merge pull request #2131 from bigchaindb/quick-fix-to-release-process-for-now

Add note at top how this is old, will be updated
This commit is contained in:
Troy McConaghy 2018-03-14 00:20:41 +01:00 committed by GitHub
commit d8893c11e7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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.
<hr>
The release process for BigchainDB server differs slightly depending on whether it's a minor or a patch release.
BigchainDB follows