kubo icon indicating copy to clipboard operation
kubo copied to clipboard
verified publisher icon ipfs

Release 0.16

Open BigLep opened this issue 3 years ago • 3 comments

Meta

  • Release owner: @galargh
  • Release reviewer: @ajnavarro
  • Expected RC date: ~2022-09-22~ 2022-09-26
  • Expected final release date: ~2022-09-29~ 2022-10-03
  • Accompanying PR for improving the release process: https://github.com/ipfs/kubo/pull/9283

See the Kubo release process for more info.

Initial planning

Themes

  1. Clean up cruft
  2. Reframe / Gateway/indexer integration
  • https://github.com/ipfs/kubo/issues/9150
  1. IPNS specs/degredation
  2. Kubo RPC libraries ? TBD
  3. Bitswap items TBD?

Items we're explicitly not doing

Items to document for users

  1. _redirects: wip in https://github.com/ipfs/ipfs-docs/pull/1275

Kubo 0.16.0 Release

We're happy to announce Kubo 0.16.0, bla bla...

As usual, this release includes important fixes, some of which may be critical for security. Unless the fix addresses a bug being exploited in the wild, the fix will not be called out in the release notes. Please make sure to update ASAP. See our release process for details.

🗺 What's left for release

  • [x] https://github.com/ipfs/kubo/pull/9265/
  • [x] https://github.com/ipfs/kubo/pull/8927
  • [x] https://github.com/ipfs/kubo/pull/9285
  • [x] https://github.com/ipfs/kubo/pull/9274
  • [ ] https://github.com/ipfs/kubo/pull/8890
  • [ ] https://github.com/ipfs/kubo/pull/9293

Ideal, but not blocking:

  • [ ] https://github.com/ipfs/kubo/issues/9297
  • [ ] https://github.com/ipfs/kubo/pull/9053

🔦 Highlights

< top highlights for this release notes. For ANY version (final or RCs) >

✅ Release Checklist

  • [ ] Stage 0 - Prerequisites
    • [ ] Ensure that the What's left for release section has all the checkboxes checked. If that's not the case, discuss the open items with Kubo maintainers and update the release schedule accordingly.
    • [x] Create docs-release-vX.Y.Z branch, open a draft PR and keep updating docs/RELEASE_ISSUE_TEMPLATE.md on that branch as you go.
  • [ ] Stage 1 - Initial Preparations
    • [x] Upgrade to the latest patch release of Go that CircleCI has published
    • [ ] Fork a new branch (release-vX.Y.Z) from master.
    • [ ] Bump the version in version.go in the master branch to vX.(Y+1).0-dev.
  • [ ] Stage 2 - Release Candidate - if any non-trivial changes need to be included in the release, return to this stage
    • [ ] Bump the version in version.go in the release-vX.Y.Z branch to vX.Y.Z-rcN.
    • [ ] If applicable, add new commits to the release-vX.Y.Z branch from master using git cherry-pick -x ...
      • Note: release-* branches are protected. You can do all needed updates on a separated branch (e.g. wip-release-vX.Y.Z) and when everything is settled push to release-vX.Y.Z
    • [ ] Tag HEAD release-vX.Y.Z commit with vX.Y.Z-rcN (git tag -s vX.Y.Z-rcN")
    • [ ] Push the release-vX.Y.Z branch to GitHub (git push origin release-vX.Y.Z).
    • [ ] Push the vX.Y.Z-rcN tag to GitHub (git push origin vX.Y.Z-rcN; DO NOT USE git push --tags because it pushes all your local tags).
    • [ ] Add artifacts to https://dist.ipfs.tech by making a PR against ipfs/distributions with local changes produced by add-version (see usage)
      • [ ] Wait for PR to build artifacts and generate diff (~30min)
      • [ ] Inspect results, merge if CI is green and the diff looks ok
      • [ ] Wait for master branch to build and update DNSLink at https://dist.ipfs.tech (~30min)
    • [ ] Cut a pre-release on GitHub and reuse signed artifacts from https://dist.ipfs.tech/kubo (upload the result of the ipfs/distributions build from the previous step).
    • [ ] Announce the RC
      • [ ] Create a new post on IPFS Discourse. This will automatically post to IPFS Discord #ipfs-chatter. Examples from the past: 0.14.0
      • [ ] Pin the topic. You need to be part of the admin group for that.
      • [ ] To the early testers listed in docs/EARLY_TESTERS.md. Do this by copy/pasting their GitHub usernames and checkboxes as a comment to the release issue so they get a GitHub notification. (example)
  • [ ] Stage 3 - Automated Testing
    • [ ] Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes:
  • [ ] Stage 4 - Internal Testing
    • [ ] CHANGELOG.md has been updated
    • [ ] Infrastructure Testing.
      • [ ] Open an issue against https://github.com/protocol/bifrost-infra and spell out all that we want (e.g.,mgateways, bootstrapper, and cluster). example https://github.com/protocol/bifrost-infra/issues/2109
      • [ ] Deploy new version to a subset of Bootstrappers
      • [ ] Deploy new version to a subset of Gateways
      • [ ] Deploy new version to a subset of Preload nodes
      • [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup
    • [ ] IPFS Application Testing - Run the tests of the following applications:
      • [ ] IPFS Desktop
      • [ ] IPFS Companion
        • Start kubo daemon of the version to release.
        • Start a fresh chromium or chrome instance using chromium --user-data-dir=$(mktemp -d)
        • Start a fresh firefox instance using firefox --profile $(mktemp -d)
        • Install IPFS Companion from vendor-specific store.
        • Check that the comunication between Kubo daemon and IPFS companion is working properly checking if the number of connected peers changes.
  • [ ] Stage 5 - Community Prod Testing
    • [ ] Documentation
      • [ ] Ensure that CHANGELOG.md is up to date
        • [ ] Add a link from release notes to Discuss post (like we did here: https://github.com/ipfs/kubo/releases/tag/v0.15.0 )
        • [ ] Keep the release notes as trim as possible (removing some of the top headers, like we did here: https://github.com/ipfs/kubo/releases/tag/v0.15.0 )
      • [ ] Ensure that README.md is up to date
      • [ ] Update docs by merging the auto-created PR in https://github.com/ipfs/ipfs-docs/pulls (they are auto-created every 12 hours) (only for final releases, not RCs)
    • [ ] Invite the wider community through (link to the release issue):
  • [ ] Stage 6 - Release
    • [ ] Final preparation
      • [ ] Verify that version string in version.go has been updated.
      • [ ] Open a PR merging release-vX.Y.Z into the release branch.
        • This should be reviewed by the person who most recently released a version of go-ipfs.
        • Use a merge commit (no rebase, no squash)
      • [ ] Prepare the command to use for tagging the merge commit (on the release branch) with vX.Y.Z.
        • Use git tag -s to ensure the tag is signed
      • [ ] Have the tagging command reviewed by the person who most recently released a version of go-ipfs
        • This is a dangerous operation, as it is difficult to reverse due to Go modules and automated Docker image publishing
      • [ ] Push the tag
        • Use git push origin <tag>
        • DO NOT USE git push --tags, as it will push ALL of your local tags
        • This should initiate a Docker build in GitHub Actions that publishes a vX.Y.Z tagged Docker image to DockerHub
      • [ ] Release published
      • [ ] Cut a new ipfs-desktop release
    • [ ] Get a blog post created
      • Submit a request using this form.
      • Notify marketing in #shared-pl-marketing-requests about the blog entry request (since the form gets spam).
      • Don't mark this as done until the blog entry is live.
    • [ ] Broadcasting (link to blog post)
      • [ ] Twitter (request in Filecoin Slack channel #shared-pl-marketing-requests)
      • [ ] Reddit
      • [ ] discuss.ipfs.io
        • A bot auto-posts this to Discord and Matrix
  • [ ] Stage 7 - Post-Release
    • [ ] Merge the release branch back into master, ignoring the changes to version.go (keep the -dev version from master).
    • [ ] Create an issue using this release issue template for the next release.
    • [ ] Make sure any last-minute changelog updates from the blog post make it back into the CHANGELOG.
    • [ ] Mark PR draft created for IPFS Desktop as ready for review.
    • [ ] Mark PR draft created from docs-release-vX.Y.Z as ready for review.

⁉️ Do you have questions?

The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #ipfs channel on Freenode, which is also accessible through our Matrix bridge.

Release improvements for next time

< Add any release improvements that were observed this cycle here so they can get incorporated into future releases. >

Items for a separate comment

< Do these as a separate comment to avoid the main issue from getting too large and checkbox updates taking too long. >

Changelog

< changelog generated by bin/mkreleaselog > (add it to a separated comment if it is too big)

❤️ Contributors

< list generated by bin/mkreleaselog >

Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:

  • Check the issues with the help wanted label in the ipfs/kubo repo
  • Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
  • Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
  • Join the discussion at discuss.ipfs.io and help users finding their answers.
  • Join the 🚀 IPFS Core Implementations Weekly Sync 🛰 and be part of the action!

BigLep avatar Aug 30 '22 14:08 BigLep

@ajnavarro @galargh : Slack thread on what's remaining before the release: https://filecoinproject.slack.com/archives/C03L0G3B4RX/p1663819594018819

BigLep avatar Sep 22 '22 04:09 BigLep

We're moving the RC1 release to Monday (2022-09-26) to give enough headway for merging What's left for release. As of now, the rest of the schedule remains unchanged.

galargh avatar Sep 22 '22 08:09 galargh

Thanks for updating the dates @galargh. To provide a bit more color, we aren't cutting the RC today because we just wrapped up the must-have work of https://github.com/ipfs/kubo/pull/9274 (and it's EOD Europoe time).

We don't do releases on Friday.

Pushing to Monday 2022-09-26 also gives us the ability to get two other items that were almost complete:

  • [x] https://github.com/ipfs/kubo/pull/8890
  • [x] https://github.com/ipfs/kubo/pull/9293

BigLep avatar Sep 22 '22 17:09 BigLep

Early testers ping for RC1 testing 😄

  • [ ] pacman.store (@RubenKelevra)
  • [ ] Infura (@MichaelMure)
  • [ ] Textile (@sanderpick)
  • [ ] Pinata (@obo20)
  • [ ] RTrade (@postables)
  • [ ] QRI (@b5)
  • [ ] Siderus (@koalalorenzo)
  • [ ] Charity Engine (@rytiss, @tristanolive)
  • [ ] Fission (@bmann)
  • [ ] OrbitDB (@tabcat)

galargh avatar Sep 26 '22 13:09 galargh

Something that needs to improved for next time in my opinion is working on the changelog before the RC. Right now someone doesn't see much on what has changes, what they should try, what they should look out for, etc.

BigLep avatar Sep 27 '22 14:09 BigLep

Agreed, it would be beneficial to have it ready in time for the RC. BTW, here's a draft changelog that @ajnavarro prepared - https://github.com/ipfs/kubo/blob/v0.16.0-rc1/docs/changelogs/v0.16.md. It's also linked from the release. At the very least we should formalise how it gets created.

galargh avatar Sep 27 '22 14:09 galargh

Remaining changelog items added in https://github.com/ipfs/kubo/pull/9315 (ready for review)

lidel avatar Sep 27 '22 19:09 lidel

Here was the state of https://github.com/orgs/ipfs/projects/16/views/7?filterQuery=iteration%3A%22kubo+0.16%22 efore moving things to the next iteration/release. I attached as XLSX because copy/paste is causing column misalignment that I don't have time to figure out.

0.16 status on 2022-10-04.xlsx

BigLep avatar Oct 04 '22 14:10 BigLep

The AMD64 version appears to not be an AMD64 binary.

benjistokman avatar Oct 09 '22 16:10 benjistokman

@benjistokman for which platform ? Macos, Linux, windows, ... ?

Jorropo avatar Oct 09 '22 19:10 Jorropo

Linux

benjistokman avatar Oct 09 '22 20:10 benjistokman

@benjistokman it's fine for me, can you show me which one is not amd64 ?

$ curl https://dist.ipfs.tech/kubo/v0.16.0/kubo_v0.16.0_linux-amd64.tar.gz | gzip -d | tar -xf -
$ cd kubo/
$ file ipfs 
ipfs: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=202ba79f9e42d51a7d310edbd97e032d6e955f27, for GNU/Linux 3.2.0, with debug_info, not stripped

$ curl https://dist.ipfs.tech/go-ipfs/v0.16.0/go-ipfs_v0.16.0_linux-amd64.tar.gz | gzip -d | tar -xf -
$ cd go-ipfs/
$ file ipfs 
ipfs: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=202ba79f9e42d51a7d310edbd97e032d6e955f27, for GNU/Linux 3.2.0, with debug_info, not stripped

Jorropo avatar Oct 10 '22 00:10 Jorropo

Nevermind I was clicking on the Darwin one. I don't know why but the rest of the binaries didn't load. Sorry.

benjistokman avatar Oct 10 '22 02:10 benjistokman

We have successfully release v0.16.0: https://github.com/ipfs/kubo/releases/tag/v0.16.0

galargh avatar Oct 12 '22 11:10 galargh