Release v0.28 RC1#789
Conversation
|
concept ACK. I'm tempted to bikeshed over "beta" vs "rc". @tcharding what do you think? |
|
Seems like we have all our pending PRs merged so this is indeed an RC release. Updated to the tip of the master and changed to RC in version number. I propose to merge & publish this RC1. |
Kixunil
left a comment
There was a problem hiding this comment.
ACK 9efa180529e917587a79268cb8bfef587640c777
Super happy about this one! :)
lol I did a comment yesterday suggesting
I don't really mind what the process is as long as I understand it. Currently I do not understand the difference between beta and rc? In this comment @dr-orlovsky you say we do a few beta releases then an rc, whats the benefit of this as opposed to just rc releases please? |
|
The diff uses |
|
FWIW I've gotten the following downstream crates building.
Please see branch We will need #790 for rc 2. |
|
Tagged and published. |
e35368f Bump 'bitcoin' crate to 0.28.0 (Roman Zeyde) Pull request description: Following rust-bitcoin/rust-bitcoin#789. ACKs for top commit: sanket1729: ACK e35368f elichai: ACK e35368f dunxen: ACK e35368f RCasatta: ACK e35368f Tree-SHA512: e97b09c220835e3af3e7c844c6275b62a1906919ef57c3017afa939b5d95b769126d5e6133b118e464506815b47f090b9ed59d6fd1ec1c6125a54bec64c3ffac
b22f3e5 fuzz: run generate-files.sh (Andrew Poelstra) ab61d7a fuzz: update generate-files.sh for recent "fuzz against released 12.3" test (Andrew Poelstra) Pull request description: Our `generate-files.sh` script got out of sync again. I will try to add a check for this to my local CI. Fixes rust-bitcoin#789 ACKs for top commit: sanket1729: ACK b22f3e5 Tree-SHA512: 35d093206e34b4f22b2b8134c675f69fa78e8cbf6e06cbd3d46abd3b42d6196317f7aec6b31b3dbc76cd979802e1efe678c9929f751c6fa2733904cbe76d823d
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-1subrelease to unlock ability forminiscriptrelease and downstream testing. The Taproot API looks final, and the pending PRs are addresses internal issues/bugs which is perfectly fine for beta releases.