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

Bump version to v0.28 #785

Closed
wants to merge 1 commit into from
Closed

Bump version to v0.28 #785

wants to merge 1 commit into from

Conversation

dr-orlovsky
Copy link
Collaborator

@dr-orlovsky dr-orlovsky commented Jan 15, 2022

Pending PRs from https://github.com/rust-bitcoin/rust-bitcoin/milestone/10, specifically:

Draft for the release info is autogenerated by GitHub, so we have to edit it. Please feel free to edit it right here, in place. Once we will be happy with it, I will add it to the CHANLELOG.md to the release commit.

What's Changed

Breaking changes

Theoretically non-breaking

These are things people shouldn't have depended on in the first place but may be considered breaking in some contexts.

New APIs/features

Bug fixes

Mildly interesting improvements

These improvements are mainly internal or documentation but may have noticeable impact on the quality of the crate.

Other/uncategorized changes

New Contributors

Full Changelog: 0.27.0...0.28.0

@dr-orlovsky dr-orlovsky added this to In process in Taproot Jan 15, 2022
@apoelstra
Copy link
Member

LOL that half the "first contributors" are established regulars now. It's been a long time since we had a release.

I guess as far as editing, maybe people should just add strikethrough text to the PR they consider too minor to mention, so we can discuss controversial ones?

@tcharding
Copy link
Member

I do not have edit permissions on the original post. All of my contributions listed are too minor to mention IMO except perhaps:

  • Improve parsing of Denomination string

@apoelstra
Copy link
Member

I've invited you to be a maintainer on this repo, so you should be able to edit the issue now.

@dr-orlovsky dr-orlovsky mentioned this pull request Jan 16, 2022
@darosior
Copy link
Contributor

I guess as far as editing, maybe people should just add strikethrough text to the PR they consider too minor to mention, so we can discuss controversial ones?

I think mine is definitely too minor to be worthy of release notes, feel free to strikethrough/remove.

@tcharding
Copy link
Member

I've invited you to be a maintainer on this repo, so you should be able to edit the issue now.

Awesome, thanks!

@vss96
Copy link

vss96 commented Jan 17, 2022

I guess as far as editing, maybe people should just add strikethrough text to the PR they consider too minor to mention, so we can discuss controversial ones?

My change is minor as well, so feel free to remove it.

@Kixunil
Copy link
Collaborator

Kixunil commented Jan 17, 2022

I strongly believe it'd be very useful to call out breaking changes separately. Will be probably hard to track them down as I'm not confident all of them have API break label.

(Also LOL at my first contribution - I believe my first was overflow bug fix long. My memory is bad, lol.)

@Kixunil
Copy link
Collaborator

Kixunil commented Jan 17, 2022

Started categorizing issues but there are many of them and have to go AFK for a bit and didn't want to risk losing the changes. (Hope it's OK given we can see edit history.)

apoelstra added a commit that referenced this pull request Jan 18, 2022
1b2dbd7 0.28.0-rc.1 release (Dr Maxim Orlovsky)

Pull request description:

  We still have quite a few issues and PRs pending to be addressed/merged before full 0.28 release: see https://github.com/rust-bitcoin/rust-bitcoin/milestone/10

  Most important, we have to find a way to address #777; additionally it will be desirable to get #587, #786, #776.

  We also have quite of work to write CHANGELOG in #785

  Nevertheless I propose to start with a `beta-1` subrelease to unlock ability for `miniscript` release and downstream testing. The Taproot API looks final, and the pending PRs are addresses internal issues/bugs which is perfectly fine for beta releases.

ACKs for top commit:
  Kixunil:
    ACK 1b2dbd7

Tree-SHA512: a7bd6dd3e7a489f7fd758fb0d7a60103bfe0cdf88997b2163f163841fa1c12e7b31fa8f03b9f817a671379578dbc10a2ca583f49b64d2d2de4a9ebb57b2b9bd5
@afilini
Copy link
Contributor

afilini commented Jan 18, 2022

I guess as far as editing, maybe people should just add strikethrough text to the PR they consider too minor to mention, so we can discuss controversial ones?

I can't directly edit the post, but I think mine aren't worth mentioning. They were mostly improvements/bugfixes to unreleased taproot code, so they also won't have any real impact to external users.

@tcharding
Copy link
Member

Strike through done for those requesting it up to now.

@tcharding
Copy link
Member

Do we want to re-release secp256k1 with Parity fixup before we release 0.28.0?

@sanket1729
Copy link
Member

@apoelstra, I think we should fix the parity along with rust-bitcoin/rust-secp256k1#378. It would simplify a lot of things for rust-miniscript downstream.

@sanket1729
Copy link
Member

I don't think we should be tagging everyone for the release notes PR.

The goal of release notes should be

  • Document breaking changes. Suggest how to fix them if they are non-trivial
  • Highlight new features and APIs that might be of interest.
  • Thank everyone for the contributions

@darosior
Copy link
Contributor

darosior commented Jan 21, 2022 via email

@dr-orlovsky
Copy link
Collaborator Author

Superseded by #915

Taproot automation moved this from In process to Done Apr 19, 2022
@tcharding
Copy link
Member

I think you meant: superseded by #944

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

Why PSBT needs separate Global struct?
8 participants