-
Notifications
You must be signed in to change notification settings - Fork 961
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
*: Prepare v0.40.0-rc.1 release #2290
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If #2248 is the main concern, shouldn't libp2p-core also get a RC instead of a new minor version?
My reasoning above was under the assumption that pretty much no one depends on any of the
Yes. Though that would imply that all other I need to give this more thought. Especially as this will not be the last time we cut a release candidate. I am now leaning towards cutting a release candidate of all the crates first, even though that is a bit of manual work. More input welcome @thomaseizinger! |
I didn't think of that but that is a good point. I agree that if we want to do RCs, then doing an RC for all crates is probably the way to go. Is a RC very different from depending on a Git revision? Perhaps we can just create an RC tag and encourage people to test with this version rather than going for all the churn of cutting a lot of RC. Even with a RC, people would have to manually update. |
With a couple of RegExs this wasn't actually that hard. I will test out the full release candidate process via a crates release of each of the |
I tagged and published the following releases:
Downstream testing with the
|
Also, given that this is a rather large release, I am happy to support with the upgrade process. Feel free to ping me on your upgrade pull request. |
|
@kpp |
#2214 Should be somehow addressed in the https://docs.rs/libp2p/0.40.0-rc.2/libp2p/swarm/trait.NetworkBehaviour.html docs. |
Good point @kpp. Do you want to propose a patch? |
Sorry, I am not sure what's the difference between event_process = false and true to write a doc about it. There is no |
The docs currently say that by default, we require NetworkBehaviour_EventProcess_. That default changed so really only the current section needs to be negated. Sorry that I missed this as part of the PR. If none beats me to it, I'll send an update in the next couple of days! |
Thank you for the release @mxinden! Our upgrade went well and everything is working as expected. |
I have cut another release candidate (tagged and published) mostly due to #2304. Let me know in case you are seeing any oddities with rc.3. If not, I would promote the release candidate to a proper release in the next couple of days. (//CC @AgeManning) |
The default behaviour changed with libp2p#2214. This updates the doc comment. Initially raised in libp2p#2290 (comment).
I am a bit confused. |
The default behaviour changed with #2214. This updates the doc comment. Initially raised in #2290 (comment).
I just branched off of With that, |
For the record |
The default behaviour changed with libp2p/rust-libp2p#2214. This updates the doc comment. Initially raised in libp2p/rust-libp2p#2290 (comment).
I would like to cut a new release of:
libp2p-XXX
)multistream-select
libp2p
crate -v0.40.0-rc.1
The reasoning for cutting release candidates for now, instead of a full release, is the amount of changes since the last release (see changelogs), especially #2248.
Any objections?