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
master
still has version set to 0.32.0-rc1
#2724
Comments
Found with: rust-bitcoin/rust-bitcoin-maintainer-tools#2 That tool is "so hot right now" :) |
So, in many projects we would set it to "0.32.99" or something goofy like that to emphasize to any users that this is a pre-release. In Rust it might make sense to put it as Alternaely we could set it to 0.32.0 as you suggest. But I don't think it's wrong for it to deviate from any release branches. |
No worries, if it doesn't matter lets just leave it as is. |
Well, I think leaving it at an rc number is still misleading and we ought to change it. It's true that it "doesn't matter" in the sense that anybody using master will be pinning by git rev rather than by semver version, but I still think we should choose something that won't be confused with a real revision. |
During the recent release cycle we left `bitcoin` on the last rc version. Set the version number to the current release, as it is for all the other crates in the workspace. Close: rust-bitcoin#2724
During the recent release cycle we left `bitcoin` on the last rc version. Set the version number to the current release, as it is for all the other crates in the workspace. Close: rust-bitcoin#2724
During the recent release cycle we left `bitcoin` on the last rc version. Set the version number to `v0.33.0-unreleased` to make it obvious what it is. Close: rust-bitcoin#2724
During the recent release cycle we left `bitcoin` on the last rc version. Set the version number to `v0.33.0-unreleased` to make it obvious what it is. Close: rust-bitcoin#2724
I've done something wrong during the release process;
master
should be on version0.32.0
now too.The text was updated successfully, but these errors were encountered: