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.

Sign up for GitHub

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

Jump to bottom

lotus v1.9.0 #5977

Closed
50 of 69 tasks
jennijuju opened this issue Apr 6, 2021 · 12 comments
Closed
50 of 69 tasks

lotus v1.9.0 #5977

jennijuju opened this issue Apr 6, 2021 · 12 comments
Assignees
@jennijuju
Labels
release
Milestone
v1.9.x

Comments

@jennijuju
Copy link
Member

jennijuju commented Apr 6, 2021 •
edited
Loading

Lotus v1.9.0 Release

🗺 What's left for the release

Note: This section is still WIP and should be finalized on Apr 9th.

🚢 Estimated shipping date

  • 2021-04-13 v1.7.0-rc1 1.9.0-rc1
  • 2021-05-03 1.9.0-rc2
  • 2021-05-06 1.9.0-rc3
  • 2021-05-14 1.9.0-rc5
  • 2021-04-27 2021-05-10 2021-05-17 v1.9.0

🔦 Highlights

Changelog

This is an optional Lotus release that introduces various improvements to the sealing, mining, and deal-making processes.

Highlights

Changes

Fixes

✅ Release Checklist

First steps:

  • Fork a new branch (release/vX.Y.Z) from master and make any further release related changes to this branch. If any "non-trivial" changes get added to the release, uncheck all the checkboxes and return to this stage.
  • Prep the changelog using bin/mkreleaselog, and add it to CHANGELOG.md
  • Bump the version in version.go in the master branch to vX.(Y+1).0-dev - Bump master version to 1.7.1-dev #6028

Prepping an RC:

  • version string in build/version.go has been updated (in the release/vX.Y.Z branch).
  • tag commit with vX.Y.Z-rcN
  • cut a pre-release here

Testing an RC:

  • Stage 0 - Automated Testing

    • Automated Testing
      • CI: Ensure that all tests are passing. * - there is one test that is flaky)
      • Testground tests

  • Stage 1 - Internal Testing

    • Upgrade our testnet infra
      • 1 bootstrap node
      • 1 miner
      • Scratch nodes
      • Wait 24 hours, confirm nodes stay in sync
      • Remaining testnet infra
    • Upgrade our mainnet infra
    • Subset of development full archival nodes
    • Subset of bootstrappers (1 per region)
    • Confirm nodes stay in sync
    • Metrics report
      • Block validation time
      • Memory / CPU usage
      • Number of goroutines
      • IPLD block read latency
      • Bandwidth usage
    • If anything has worsened significantly, investigate + fix
    • Confirm the following work (some combination of Testground / Calibnet / Mainnet / beta users)
      • Seal a sector
      • make a deal
      • Submit a PoSt
      • (optional) let a sector go faulty, and see it be recovered

  • Stage 2 - Community Dev Testing

    • Inform beta miners (@lotus-early-testers-miner in Filecoin Slack #fil-lotus)
    • Ask close ecosystem partners to test their projects (@lotus-early-testers-eco-dev in Filecoin slack #fil-lotus)
      • Powergate
      • Glif
      • Zondax
      • Stats dashboard
      • Community dashboards
      • Infura
      • Sentinel
      • Protofire
      • Fleek

  • Stage 3 - Community Prod Testing

    • Documentation
    • Invite the wider community through (link to the release issue):
      • Create a lotus disucssion, example here
      • Link the disucssion in #fil-lotus on Filecoin slack

  • Stage 4 - Release

    • Final preparation
      • Verify that version string in version.go has been updated.
      • Ensure that CHANGELOG.md is up to date
      • Ensure that README.md is up to date
      • Merge release-vX.Y.Z into the releases branch.
      • Tag this merge commit (on the releases branch) with vX.Y.Z.
      • Cut the release here.
      • Final announcements
        • Update network.filecoin.io
        • Add a comment when the final release is tagged, example here
        • repost in #fil-lotus in filecoin slack

  • Post-Release

    • Merge the releases branch back into master, ignoring the changes to version.go (keep the -dev version from master).
    • Update RELEASE_ISSUE_TEMPLATE.md with any improvements determined from this latest release iteration.
    • Create an issue using RELEASE_ISSUE_TEMPLATE.md for the next release.

❤️ Contributors

< list generated by bin/mkreleaselog >

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

  • TODO

⁉️ Do you have questions?

Leave a comment here
@jennijuju
Copy link
Member Author

@dirkmc IIUC, the new market release is not 100% backward compatible and we may want to avoid that if possible. Do we have plans to fix that? If so, can it be done by next Monday?

@dirkmc
Copy link
Contributor

dirkmc commented Apr 7, 2021

I will do a test as part of #5941 to check if the release is backwards compatible between 1.6.0 and 1.7.0

@f8-ptrk
Copy link
Contributor

f8-ptrk commented Apr 7, 2021

4 - ensure the docs are in sync

@vanvank
Copy link

vanvank commented Apr 8, 2021

can we upgrade using the latest master which is 1.7.0 for April 12th

@ProgramAPE
Copy link

The version of rust-fil-proofs will be changed to 1.6.0? Why not the 6.1.0+ series?

@BigLep BigLep added this to the Lotus 1.7 milestone Apr 8, 2021
@BigLep BigLep changed the title lotus v1.7.0 lotus vNext Apr 9, 2021
@BigLep BigLep changed the title lotus vNext lotus v$next Apr 9, 2021
@BigLep
Copy link
Member

BigLep commented Apr 9, 2021

Note that while this was previously listed as Lotus v1.7.0, we have redacted this to v$next until #5948 get addressed, which covers Lotus version naming and how it relates to Network versions.

@jennijuju
Copy link
Member Author

modularized lotus-miner wouldnt get in this release

@jennijuju jennijuju changed the title lotus v$next lotus v1.70 Apr 12, 2021
@jennijuju
Copy link
Member Author

The team has decided on the version convention philosophy and will update in the discussion and have it in lotus readme soon. but as the result of that conversation, this release will be a feature release that has version v1.7.0

@raulk raulk changed the title lotus v1.70 lotus v1.7.0 Apr 12, 2021
@magik6k magik6k mentioned this issue Apr 13, 2021
Merged
@BigLep BigLep changed the title lotus v1.7.0 lotus v1.9.0 Apr 29, 2021
@jennijuju jennijuju changed the title lotus v1.9.0 lotus v1.9.2 Apr 30, 2021
@jennijuju jennijuju changed the title lotus v1.9.2 lotus v1.9.1 Apr 30, 2021
@jennijuju jennijuju changed the title lotus v1.9.1 lotus v1.9.0 Apr 30, 2021
@jennijuju jennijuju modified the milestones: Lotus 1.9.0, v1.9.x Apr 30, 2021
@BigLep BigLep pinned this issue May 3, 2021
@BigLep BigLep mentioned this issue May 3, 2021
Closed
@jennijuju
Copy link
Member Author

proof v7.0.0 appears to have issue with gpu as well and this is currently blocked by it

@jennijuju
Copy link
Member Author

proof v7.0.0 appears to have issue with gpu as well and this is currently blocked by it

this is done now

@BigLep
Copy link
Member

BigLep commented May 7, 2021

@jennijuju : FYI I updated the dates in "Estimated shipping date". Feel free to adjust further.

@BigLep
Copy link
Member

BigLep commented May 12, 2021

@jennijuju : FYI I added checklist steps for going back and updating the release template based on lessons learned. This is in the template as well in #6236

@jennijuju jennijuju unpinned this issue May 18, 2021
@BigLep BigLep assigned jennijuju and unassigned jennijuju Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jennijuju jennijuju

Labels
release
Projects
None yet
Milestone
v1.9.x
Development

No branches or pull requests
6 participants
@BigLep @dirkmc @ProgramAPE @vanvank @jennijuju @f8-ptrk