From 4686ebb4200bcdd0d0f572076bc59bbd8541c10c Mon Sep 17 00:00:00 2001 From: Tobin Harding Date: Sat, 16 Jan 2021 08:45:04 +1100 Subject: [PATCH] Add full stops to list items Super anal patch to make list items uniform, add full stop to the items where it is missing. --- DEVELOPMENT_CYCLE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DEVELOPMENT_CYCLE.md b/DEVELOPMENT_CYCLE.md index 74d730c1..6d733fbd 100644 --- a/DEVELOPMENT_CYCLE.md +++ b/DEVELOPMENT_CYCLE.md @@ -27,11 +27,11 @@ Pre-`v1.0.0` our "major" releases only affect the "minor" semver value. Accordin 1. Create a new branch called `release/x.y.z` from `master`. Double check that your local `master` is up-to-date with the upstream repo before doing so. 2. Make a commit on the release branch to bump the version to `x.y.z-rc.1`. The message should be "Bump version to x.y.z-rc.1". 3. Push the new branch to `bitcoindevkit/bdk` on GitHub. -4. During the one week of feature freeze run additional tests on the release branch +4. During the one week of feature freeze run additional tests on the release branch. 5. If a bug is found: - If it's a minor issue you can just fix it in the release branch, since it will be merged back to `master` eventually - For bigger issues you can fix them on `master` and then *cherry-pick* the commit to the release branch -6. Update the changelog with the new release version +6. Update the changelog with the new release version. 7. On release day, make a commit on the release branch to bump the version to `x.y.z`. The message should be "Bump version to x.y.z". 8. Add a tag to this commit. The tag name should be `vx.y.z` (for example `v0.5.0`), and the message "Release x.y.z". Make sure the tag is signed, for extra safety use the explicit `--sign` flag. 9. Push the new commits to the upstream release branch, wait for the CI to finish one last time.