Release tracking PR: psbt-v2 v0.3.0#85
Conversation
|
@tcharding I might be jumping the gun here, but figured can always update the changelog later if necessary. |
nyonson
force-pushed
the
zero-three-zero-docs
branch
from
d5d88c2 to
673fae0
Compare
nyonson
force-pushed
the
zero-three-zero-docs
branch
from
673fae0 to
3783ddf
Compare
|
Want to do the arbitrary stuff in this release or do it later and do a |
I'll sneak it into |
|
Is this the release tracking PR? If so can you use the same title format we (I) do in |
|
|
||
| # 0.3.0 - 2026-03-24 | ||
|
|
||
| The 0.3.0 version is the last major release for `bitcoin v0.32.x`. Only security patches will be added to the v0.3.x branch. |
There was a problem hiding this comment.
Should we go ahead and create this branch?
There was a problem hiding this comment.
Open to input on this one since I don't have a ton of experience with this model. But I was thinking we tag the commit we publish with v0.3.0 and then if we have need to do any security releases, we then lazily branch at that point a v0.3.x branch.
There was a problem hiding this comment.
Sounds good to me. I was thinking in the PRs to fix the issues opened, and if I should open them now or wait until v0.3.0.
tcharding
changed the title
v0.3.0psbt-v2 v0.3.0
|
Shall we do these two before releasing this fellas? |
I would say no. We want at least a release with the minimal differences possible, right? |
|
I just went ahead and pulled the trigger. Tagged and published. |
3 participants
No description provided.