Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.0.0-alpha.11 #1435

Closed
28 tasks done
notmandatory opened this issue May 9, 2024 · 2 comments · Fixed by #1437
Closed
28 tasks done

Release 1.0.0-alpha.11 #1435

notmandatory opened this issue May 9, 2024 · 2 comments · Fixed by #1437
Assignees
Labels
release Release related issue or PR
Milestone

Comments

@notmandatory
Copy link
Member

notmandatory commented May 9, 2024

Create a new minor release

Summary

This incremental bi-weekly release includes three big improvements. New electrum full_scan and sync APIs were added for more efficiently querying blockchain data. And the keychain::Changeset now includes public key descriptors and keychain::Balance uses bitcoin::Amount instead of u32 sats amounts. See the changelog for all the details.

Commit

TBD

Changelog

Changed

Checklist

Release numbering must follow Semantic Versioning. These steps assume the current master branch development version is 1.0.0-alpha.11.

On the day of the feature freeze

Change the master branch to the 1.0.0-alpha.11 version:

  • Switch to the master branch.
  • Create a new PR branch called bump_dev_1.0.0_alpha.11.
  • Bump the bump_dev_1.0.0_alpha.11 branch to the next development MINOR+1 version.
    • Bump the modified crates versions in their Cargo.toml files. [update this list with only changed crates]
      • bdk
      • bdk_chain
      • bdk_bitcoind_rpc
      • bdk_electrum
      • bdk_esplora
      • bdk_file_store
      • bdk_testenv
      • bdk_persist
    • The commit message should be: [update this list with only changed crates]
      Bump bdk version to 1.0.0-alpha.11
      
      bdk_chain to 0.14.0
      bdk_bitcoind_rpc to 0.10.0
      bdk_electrum to 0.13.0
      bdk_esplora to 0.13.0
      bdk_file_store to 0.11.0
      bdk_testenv to 0.4.0
      bdk_persist to 0.2.0
      
  • Create PR and merge the bump_dev_1.0.0-alpha.11 branch to master.
    • Title PR "Bump bdk version to 1.0.0-alpha.11".

On the day of the release

Tag and publish new release:

  • Add a tag to the HEAD commit in the master branch.
    • The tag name should be v1.0.0-alpha.11
    • The first line of the tag message should be "Release 1.0.0-alpha.11".
    • In the body of the tag message put a copy of the Summary and Changelog for the release.
    • Make sure the tag is signed, for extra safety use the explicit --sign flag.
  • Wait for the CI to finish one last time.
  • Push the new tag to the bitcoindevkit/bdk repo.
  • Publish all the updated crates to crates.io. [update this list with only changed crates]
    • bdk_chain
    • bdk_testenv
    • bdk_bitcoind_rpc
    • bdk_electrum
    • bdk_esplora
    • bdk_persist
    • bdk_file_store
    • bdk
  • Create the release on GitHub.
    • Go to "tags", click on the dots on the right and select "Create Release".
    • Set the title to Release 1.0.0-alpha.11.
    • In the release notes body put the Summary and Changelog.
    • Use the "+ Auto-generate release notes" button to add details from included PRs.
    • Until we reach a 1.0.0 release check the "Pre-release" box.
  • Make sure the new release shows up on crates.io and that the docs are built correctly on docs.rs.
  • Announce the release, using the Summary, on Discord, Twitter and Nostr.
  • Celebrate 🎉
@notmandatory notmandatory added the release Release related issue or PR label May 9, 2024
@notmandatory notmandatory added this to the 1.0.0-alpha milestone May 9, 2024
@notmandatory notmandatory self-assigned this May 9, 2024
@notmandatory notmandatory added this to BDK May 9, 2024
@notmandatory notmandatory moved this to Todo in BDK May 9, 2024
@notmandatory notmandatory moved this from Todo to Needs Review in BDK May 10, 2024
@ValuedMammal
Copy link
Contributor

ValuedMammal commented May 10, 2024

Some versions in the issue template appear off. bdk_persist is ahead by one again. Electrum and esplora should have same version?

I'm not sure the above changelog reflects what ultimately ended up in 1203

@notmandatory
Copy link
Member Author

notmandatory commented May 10, 2024

Thanks for double checking the versions bumps, they should be correct now. For #1203, #1403, #1411 I simplified the changelog by only using the PR titles, anyone who needs details can do the diffs.

@github-project-automation github-project-automation bot moved this from Needs Review to Done in BDK May 10, 2024
@notmandatory notmandatory changed the title Release MAJOR.MINOR+1.0Release 1.0.0-alpha.11 Release Release 1.0.0-alpha.11 May 23, 2024
@notmandatory notmandatory changed the title Release Release 1.0.0-alpha.11 Release 1.0.0-alpha.11 May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Release related issue or PR
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants