chore: Prepare rust-libp2p v0.50.0 release #3163
Conversation
| @@ -1,6 +1,6 @@ | |||
| [package] | |||
| name = "libp2p-webrtc" | |||
| version = "0.1.0-alpha" | |||
| version = "0.4.0-alpha" | |||
#3157 not sure this is a blocker, but I'd love to get it fixed before 0.50 |
|
could we also include #3128 ? |
|
I'd like to get #3144 fixed before releasing QUIC. I am currently working on it. But I doesn't have to be a blocker. |
|
QUIC together with dcutr would be a big deal... |
|
any chance for #2712 to make it? |
|
I suggest we only block releases on bug fixes, e.g. #3144. Blocking on features I made the experience that the release process drags along for a long time. Once any of the above features are merged, I am happy to cut a follow-up release, in case that is helpful for folks.
I would not consider this a bug and thus suggest not blocking on it. In case it makes it in, great. In case it doesn't, again happy to cut a follow-up release.
I will take a look. I don't consider this a bug fix though.
Bug fix. Sounds good to me.
@geotro this is a larger endeavor and thus will not make it in time.
Not a bug, thus I suggest not blocking on it. That said, in case it makes it in time, great! //CC @kpp and @melekes as this requires adjustments on the Substrate side. |
|
Tagged and published the following crates:
|
Description
Notes
I propose we cut a new release, namely
v0.50.0.I included a small paragraph highlighting quic, tls and webrtc. Happy to highlight additional user-facing changes. Proposals welcome.
Milestone 4 tracks the outstanding items before we can cut the release. In case you would like to see something included not yet part of milestone 4, please speak up.