Skip to content
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

go-libp2p v0.22 #1631

Closed
15 of 39 tasks
marten-seemann opened this issue Jul 1, 2022 · 1 comment
Closed
15 of 39 tasks

go-libp2p v0.22 #1631

marten-seemann opened this issue Jul 1, 2022 · 1 comment

Comments

@marten-seemann
Copy link
Contributor

marten-seemann commented Jul 1, 2022

🗺 What's left for release

AutoRelay Polling

Consolidation

Tracking issue: #1556

Misc

🔦 Highlights

This release finishes our long-term effort of consolidating repositories (#1556), turning go-libp2p into a mono-repo. In this release, we've moved the last 4 remaining repositories here:

As with our last consolidation release (v0.20.0), this means that some import paths might have changed. The recommended way of updating is the following:

  1. Run go get -u ./.... This will pull in updated dependencies, including updates for all the repositories listed above.
  2. Run staticcheck ./.... All repositories listed above were deprecated, and staticcheck will generate errors when they are imported.

Other noteworthy changes.

< top highlights for this release notes >

Changelog

< changelog generated by scripts/mkreleaselog >

✅ Release Checklist

  • Stage 0 - Finishing Touches
    • Go through relevant libp2p repos looking for unreleased changes that should make it into the release. If you find any, cut releases.
    • Run go get -u ./... to see if there are any out-of-date deps that look important. If there are, bubble them. Try to avoid directly updating indirect deps in go-libp2p's go.mod when possible.
    • Make sure local tests are passing.
  • Stage 1 - Upstream Testing
    • Create testing branches in lotus & go-ipfs with the new go-libp2p release and run CI/tests. Many upstream projects are tested in CI, but lotus & go-ipfs are not.
    • (someday) Run upstream testground tests. Unfortunately, this is too time consuming at the moment.
      • (someday) Run bitswap testground tests.
      • (someday) Run DHT testground tests.
  • Stage 2 - Infrastructure Testing
    • How: Using the testing branches created above, work with the infrastructure team to deploy the new libp2p versions to our infrastructure.
    • Where:
      • A go-ipfs gateway.
        • Deploy
        • Analyze
          • Look at pprof profile dumps, especially CPU profiles and heap allocation profiles, noting any significant changes.
      • A go-ipfs bootstrapper.
        • Deploy
        • Analyze
          • Look at pprof profile dumps, especially CPU profiles and heap allocation profiles, noting any significant changes.
          • Check peers (e.g., ipfs swarm peers) to make sure we're connecting to peers on all transports.
          • Check advertised addresses and protocols (e.g., ipfs id) to make sure they're sane.
  • Stage 3 - Release
    • Tag the release on master.
    • Publish the release through the GitHub UI, adding the release notes. Some users rely on this to receive notifications of new releases.
    • Announce the release on the discuss.libp2p.io.
  • Stage 4 - Update Upstream
  • deprecate repos
  • Make required changes to the release process.
@BigLep BigLep added this to go-libp2p Aug 12, 2022
@BigLep BigLep moved this to 🥞 Todo in go-libp2p Aug 12, 2022
@BigLep
Copy link
Contributor

BigLep commented Aug 26, 2022

Closing since release happened (https://github.com/libp2p/go-libp2p/releases/tag/v0.22.0 ) and release process updated were made.

@BigLep BigLep closed this as completed Aug 26, 2022
Repository owner moved this from 🥞 Todo to 🎉 Done in go-libp2p Aug 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants