From 18f1107c41b2b2e4e2d4b4c7b1460fc2a17dd239 Mon Sep 17 00:00:00 2001 From: Steve Myers Date: Thu, 30 Sep 2021 13:38:16 -0700 Subject: [PATCH] Update DEVELOPMENT_CYCLE release instructions --- DEVELOPMENT_CYCLE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DEVELOPMENT_CYCLE.md b/DEVELOPMENT_CYCLE.md index 7e116053..c2392ddf 100644 --- a/DEVELOPMENT_CYCLE.md +++ b/DEVELOPMENT_CYCLE.md @@ -39,7 +39,7 @@ Pre-`v1.0.0` our "major" releases only affect the "minor" semver value. Accordin 11. Publish **all** the updated crates to crates.io. 12. Make a new commit to bump the version value to `x.y.(z+1)-dev`. The message should be "Bump version to x.y.(z+1)-dev". 13. Merge the release branch back into `master`. -14. If the `master` branch contains any unreleased changes to the `bdk-macros`, `bdk-testutils`, or `bdk-testutils-macros` crates, change the `bdk` Cargo.toml `[dev-dependencies]` to point to the local path (ie. `bdk-testutils-macros = { path = "./testutils-macros"}`) +14. If the `master` branch contains any unreleased changes to the `bdk-macros` crate, change the `bdk` Cargo.toml `[dependencies]` to point to the local path (ie. `bdk-macros = { path = "./macros"}`) 15. Create the release on GitHub: go to "tags", click on the dots on the right and select "Create Release". Then set the title to `vx.y.z` and write down some brief release notes. 16. Make sure the new release shows up on crates.io and that the docs are built correctly on docs.rs. 17. Announce the release on Twitter, Discord and Telegram.