Revamp go-libp2p Release Flow

[daviddias]

Hi libp2p Team 👋

As you might have noticed, go-ipfs is doing a big push to re-haul its release process -- ipfs/kubo#6482 -- and we realized that in order for it to be a successful and smooth operation, we will need your collaboration. More concretely, it would be awesome to:

• Detach releases of go-ipfs from go-libp2p. This will enable go-ipfs to only worry about latest changes on go-ipfs code when performing a release
• Revamp the go-libp2p release flow and include partner testing (one of the partners being go-ipfs)
• Include some kind of semantic versioning that we can rely on (e.g. 0.0.X -> patch version, something we know we can trust and update while doing a release vs. 0.X.0 -> minor version, a warning to not update without even more rigorous and new testing)

Adopting a revamped release flow will mimic in someways the synergy that exists between js-libp2p release flow and js-ipfs release flow that enables both projects to co-exist and co-release without blocking one on the other.

How does this sound at first glance to you?

It might be better to use the next Monday sync to talk about this in more detail, nevertheless I wanted to kick off things with an issue to start planting the seeds for thought :)

[marten-seemann]

I think our current release flow captures this pretty well.