Release 0.18 about kubo HOT 28 CLOSED

🎉 Kubo v0.18.0 is out!

from kubo.

v0.18.0-rc2 is out 🥳

from kubo.

For those watching the issue, realistically this release won't be happening until Monday, 2023-01-23, because code changes won't be in until EOD Thursday, 2023-01-19, and we don't do releases on Friday.

from kubo.

2022-12-07 update:

We aren't going to be ready for an RC early Thursday, 2022-12-08.

The previous "nice to haves" have become "required" since some of the "required" items needed a repo migration. Since we were already going to be doing a repo migration anyways, we're taking on all the things (including the previous "nice to haves") for the repo migration.

The issue description is the ultimate source of truth but we have these tracks of work:

1. (@Jorropo @lidel): Repo migrations. This is related to multiple features. We want to publish @Jorropo's (#9410 ) first and then @lidel will put additional migrations on top.
2. (@Jorropo): go-lipbp2p 0.24 upgrade: #9423
3. (@lidel unless he defers to @ajnavarro): Review/merge the resource manager docs: #9468

@Jorropo or @lidel : please callout if there is work that other can help you with like @ajnavarro .

We'll talk about the 0.18 RC date during Kubo standup on 2022-12-08.

In summary @galargh : there isn't anything for you to immediately jump on concerning 0.18 when you start work on 2022-12-08. That said, lets please make sure we've got Bifrost engaged for the deployments we'll want them to do. (I'm hopeful we can do one-box deployments early Friday so we get data over the weekend.)

from kubo.

Going forward with 0.18.0.

from kubo.

2022-12-11 Update
@Jorropo and @lidel have been pushing forward (thank you both). I have updated the issue description to my knowledge. Quick summary of what's remaining before we can start the RC:

• End to end tests and review of ipfs/fs-repo-migrations#162 . I believe @lidel will be away 2022-12-12. @ajnavarro are you able to help review here? Otherwise please feel free to defer to @guseggert .
• (@Jorropo ) Small code changes for #9292
• @Jorropo : switch Kubo to new migrations by bumping the hardcoded CID

@Jorropo : please correct if I have any of this wrong.

@galargh : unless things change with more updates here, I don't believe we're ready for an RC when you start 2022-12-12.

@ajnavarro : if you're not able to handle with items above, feel free to start on "Items to during the RC phase before the final release" listed in the description.

from kubo.

The maintainers have identified some additional code changes to be made for this release:

Removing footguns observed in the 0.18 RC phase:

• #9545
  • PR: #9555
• #9549
  • PR: #9560
• #9548

Supporting key user:

• #9542

from kubo.

Heads-up from libp2p: We're planning to release a v0.24.1 patch release before the kubo final release: libp2p/go-libp2p#1940. As this is a patch release, updating will be trivial (no breaking changes, by definition).

You might want to consider putting this on the checklist for the final release.

from kubo.

Blocking items are resolved.
@galargh I think we are good to go for the release on Monday.

from kubo.

Agreed @galargh - please proceed with the release.
I know we havne't had full confirmation on the Bifrost deployment, but it has been deployed to some banks for days and we're not getting reports back of problems. If there are problems that can't wait for 0.19, we can do a patch release sooner (0.18.1).
Thanks!

from kubo.

I cherry-picked all the new commits from master to the release-v0.18 branch and I'm ready to proceed with the release. Waiting for confirmation from @lidel whether to proceed with 0.18.0 or 0.18.0-RC3 in the light of https://github.com/protocol/bifrost-infra/issues/2221#issuecomment-1400091522.

from kubo.

I don't knows how that will play exactly into the release process but we will have to publish a migration binary to dist.ipfs.io too, that will get downloaded by Kubo, I guess it needs to be released before or when Kubo is released to avoid race conditions where kubo can't find the migration binary.

from kubo.

@Jorropo: how are the things on your stack going:

1. ipfs/fs-repo-migrations#162
2. #9423
3. #9292

I assume this isn't completing 2022-12-08, but let me know you're estimating so we can make it clear in the release issue. Please also raise if it would helpful to have others helping.

from kubo.

2022-12-08 update:

We are not ready yet to release on 2022-12-09. We have these open items (also in issue description):

• go-libp2p 0.24 update
  • #9423
    • @Jorropo : do you want to ask others on this? I assume most of the reviews/releases can be done by others.
  • @Jorropo: #9410
• #9292 (depends on libp2p 0.24 update)
  • @Jorropo doing the coding
  • @lidel maybe can handle changelog/docs?
• #9389
  • @lidel I assume you'll take the kad-dht merges/release
• (@Jorropo) Kubo PR with CID to new migration from fs-repo-migrations

@galargh : as you can see, we're not ready for you to jump into a release for your Friday morning. Thanks for being ready though.

from kubo.

Thanks for the update! I updated the dates in the issue too.

from kubo.

2022-12-09 Update
We're not ready to execute the release yet. We're targeting 2022-12-12. The issue description tracks what is remaining.

from kubo.

@BigLep this is correct.

• ipfs/fs-repo-migrations#162
  @lidel took the 45% I made and made it 95% complete. I just finished the last 5% so we now only need someone that will:
  • Review it (I've reviewed @lidel's part and I belive he looked over mine, so it's should be really quick)
  • Merge it
  • Tag it (must be fs-repo-12-to-13/v1.0.0)
  • Release it on dist.ipfs.io
• #9292 has an attached PR that should be good: #9492 (altho CI might not agree).
  Remaining work on this:
  • Review.
  • Once the migration is available live on dist, update the hardcoded CID.
  • Ensure CI is green (it probably will be)
  • Merge it

Then everything required will be closed for Kubo 0.18-rc1 and someone will be able to care of the Kubo release.

from kubo.

@Jorropo added my review on both PRs

from kubo.

2022-12-12 update
All PRs to merge for the 0.18 RC have been satisfied.
I did some changelog updates as well (including adding a section about resource manager): #9497

@galargh : I believe you can merge the changelog update PR (#9497 ) and start the RC.

Thank you!

from kubo.

2022-12-13 conversation:
We are planning an RC2 in first week of January. Specific issues to address by them will listed later in the week.

from kubo.

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 (@aphelionz)

You're getting this message because you're listed here. Please update this list if you no longer want to be included.

from kubo.

2023-01-03 maintainer conversation:

RC2 will be cut/released on 2023-01-04. It will have the latest fixes in master, including a go-libp2p update which addresses some panics.

Before the final release we'll address these items:

• #9511
• #9482

Nice to haves for the final release (but non-blocking):

• #9506
• #9465

from kubo.

2023-01-12 release update:

1. All the required code changes are in (#9538 needs to be merged)
2. We're waiting on more production deployment validation: https://github.com/protocol/bifrost-infra/issues/2221
   Realistically final release is looking like Monday, 2023-01-16.

from kubo.

• Would be good to include #9550 so cid.contact knows which versions of Kubo are sending requests.

from kubo.

• A new bug found that I think we must consider adding into this release too: #9559

from kubo.

• Flag: 0.18.0-rc2 changes behavior when requesting JSON stored on UnixFS as application/json: https://github.com/protocol/bifrost-infra/issues/2290#issuecomment-1387347574, we need to address it before release (update specs, Kubo implementation, or both).

from kubo.

2023-01-19 kubo standup summary on where we are with the release:

Blocking the release:

• #9566
• #9555
• #9563

Best effort:

• #9548
  • We're not going to rush this, but rather focus on doing this right.
• #9542
  • We'll land as soon as the underlying pubsub library is updated

Definitely not happening:

• ResourceMgr
  • #9559
    • Dependent on a go-libp2p release
  • #9576
    • Dependent on a go-libp2p release
  • #9577
    • Needs analysis, probably dependent on a go-libp2p release
• #9530
  • Will handle in the next release after more measurements

from kubo.

The v0.18.0 release is complete! Here's a link to the issue for the next one - v0.18.1 - #9579

from kubo.