Replies: 2 comments 3 replies
-
|
Looking through the list, it would be great to have at least the following PRs included in the next release:
@jxs @dariusc93 @guillaumemichel what other PRs / issues should be in before the next relase? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
yup, thanks Darius, also #4967 and #5728 and I'd like to wait for #5724 if possible, I know we can then depend on it explicitly after being released, but I'd like to export it via |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure about #5728; getting the necessary fuzzy testing might take a bit longer, so I wouldn't block on that, see #4650 (comment). It's nothing urgent anyway, is it? Waiting for the three other PRs you mentioned:
sounds good to me. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Benno!
no pressure at all, this also helps us drive forward with the release process, as when there isn't any formal interest we have been waiting for more changes to accumulate and bundle into a release. |
Beta Was this translation helpful? Give feedback.
-
I'm working at Autonomi and we have a few PRs that were merged recently-ish. (#5507 , #5705) I'm wondering when a next release will be cut. The releases have been quite frequent this year, but the last release was 3 months ago currently.
Sorry for asking this question. I do not want to put pressure on the rust-libp2p team in any way here. Perhaps there are other channels where discussions surrounding releases happens. Let me know if there's anything I can help with.
Beta Was this translation helpful? Give feedback.
All reactions