go-libp2p
go-libp2p copied to clipboard
simplify the release checklist
This updates the release checklist to what we've actually been doing. Updating kad, pubsub, daemon and bitswap is quite a lot of work, and doesn't provide much value, given that these projects are all used by go-ipfs and lotus anyway.
I'm also not happy with Stage 2. Infrastructure testing is certainly helpful for some releases, but definitely for all. Most importantly, it requires the IPFS integration to be finished at the time that go-libp2p is released, which is not always the case. I'll leave the cleanup of that step for a later PR.
@BigLep Have you had the chance to look at this PR?
Closing because there have been followup PRs to the release process.