I'd like to ship 0.4.19 before the new year, or at least immediately after. Any PRs/changes to take into account?
PRs that look like they're pretty much ready:
I'd also like to fix: https://github.com/libp2p/go-libp2p/issues/510 first, if possible.
Major user-facing changes as I see them:
What's the plan on this one? Just curious. I'd love to ship the BS improvements :)
BS improvements :)
I mean Bitswap... but might be an apt description.
We just ran into an issue with Textile around https://github.com/libp2p/team-mgmt/issues/15#issue-380927291. I'm planning on talking with them today.
Unfortunately, my week has been captured by the libp2p team week.
Update for @ianopolous, @cboddy.
So, I said "we'll definitely cut a new release before the new year". Unfortunately, we made a mistake and changed something OpenBazaar was relying on several releases ago. They have a forked network so this has gone unnoticed for a while.
This release was supposed to fix that by reverting the change. Unfortunately, it turns out that Textile (using the main network) is relying on this new feature that we just removed so we've blocked the release on coming up with an acceptable solution. We will try to get this through as fast as possible but can't rush this.
See: https://github.com/libp2p/specs/issues/111#issuecomment-456213112
Thanks for the heads up @Stebalien
Status:
Blocked by https://github.com/ipfs/go-ipfs/issues/6007.
are we still blocked by something here? the dependency issues mentioned itt look to be all closed
@parkan we have released first release candidate and we will wait a few days to collect feedback.
Release pending in https://github.com/ipfs/go-ipfs/pull/6026.
Ok, so, a few more blockers:
~And another! https://github.com/ipfs/go-ipfs/issues/6028~
I'd like to merge https://github.com/ipfs/go-ds-flatfs/pull/52 (old bug, just showing up now) and then immediately cut a release (tomorrow). Speak now or wait till 0.4.20.
Should this issue be closed since 0.4.19 has been released?
Yes. Thanks!
Most helpful comment
Status: