lotus v1.10.0

[jennijuju]

Lotus v1.10.0 Release

🗺 What's left for the release

https://github.com/filecoin-project/lotus/milestone/16

🚢 Estimated shipping date

Please see #6283

🔦 Highlights

Changelog

Highlights

Changes

Fixes

✅ Release Checklist

Note for whomever is owning the release: please capture notes as comments in this issue for anything you noticed that could be improved for future releases. There is a Post Release step below for incorporating changes back into the RELEASE_ISSUE_TEMPLATE, and this is easier done by collecting notes from along the way rather than just thinking about it at the end.

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 scripts/mkreleaselog, and add it to CHANGELOG.md
• Bump the version in version.go in the master branch to vX.(Y+1).0-dev.

Tracking items for rc2:

• Butterfly testing
• [NV13] Mpool will reject sufficiently large batch prove commits #6338
• Update to latest FFI with Bellman fixes #6394
• Add Miner message cost configuration for ProveCommitAggregated and PreCommitBatches #6407
• CommitBatcher getSectorDeadline should check the earlier PreCommit expiry in the batch #6412
• Investigate precommit message size and whether we'll exceed thresholds #6423
• Integrate updated actor

Tracking items for rc3:

• Support early finalization before commit #6431
• Update to the new ffi to have the multicore SDR enabled by default #6450

rc4 contained no new fixes but fixed an issue with how rc3 was cut
rc5 contained a minor fix that would affect miners during the upgrade window (PR #6504)
rc6 contained ...

Tracking items for rc7:

• Any bug fixes from calibration / rc3-6 testing
• Commit aggregate is 2x bigger than expected #6515
• [BUG] Delayed message propagation on network setup #6396
• Make "Circle CI tests green" for Hyperdrive #6380
• Large scale testing post FIP13/FIP8 #6156
• E2E Testing for FIP8 & FIP13 #6157
• Expand TestPledgeBatching to test to test message propagation. #6352
• Update the default fees in configuration #6422
• Lotus fetches drand from chain backwards with null blocks while specs fetches forward #3613
• Any bug fixes from running the tests that were created in the issues above

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.
    • Testground tests

• Stage 1 - Internal Testing

  • Binaries
    • Ensure the RC release has downloadable binaries
    • Validate the binary is able to run on at least one platform
  • 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 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
    • Ensure that CHANGELOG.md is up to date
    • Check if any config updates are needed
  • Invite the wider community through (link to the release issue):
    • Check Create a discussion for this release when tagging for the major rcs(new features, hot-fixes) release
    • 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.
      • Check Create a discussion for this release when tagging the release
    • Final announcements
      • Update network.filecoin.io for mainnet, calib and nerpa.
      • repost in #fil-lotus in filecoin slack
      • Inform node provides (Protofire, Digital Ocean..)

• Post-Release

  • Merge the releases branch back into master, ignoring the changes to version.go (keep the -dev version from master). Do NOT delete the releases branch when doing so!
  • 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

💙Thank you to all the contributors!

Contributor	Commits	Lines ±	Files Changed
@magik6k	81	+9606/-1536	361
@arajasek	41	+6543/-679	189
@ZenGround0	11	+4074/-727	110
@anorth	10	+2035/-1177	55
@iand	1	+779/-12	5
@frrist	2	+722/-6	6
@Stebalien	6	+368/-24	15
@jennijuju	11	+204/-111	19
@vyzo	6	+155/-66	13
@coryschwartz	10	+171/-27	14
@Kubuxu	4	+177/-13	7
@ribasushi	4	+65/-42	5
@travisperson	2	+11/-11	4
@kirk-baird	1	+1/-5	1
@wangchao	2	+3/-2	2

⁉️ Do you have questions?

Leave a comment here if you have any questions.

[Fatman13]

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

Is "optional release" a typo?

[ROXtiGerf]

does all the box need to be ticked to finish this release?

[BigLep]

We're planning to do initiate an RC on Tuesday, 2021-06-01. The final release date is still TBD. We'll update here when the RC is available.

[BigLep]

I specified in the description above what tasks we're waiting on before rc2 and rc3.

[arajasek]

There will be no RC7, since no real code changes have landed since RC6.

[jennijuju]

https://github.com/filecoin-project/lotus/releases/tag/v1.10.0

[BigLep]

Per 2021-06-24 standup, reopening until we have gone through and confirmed that all the items (including post release items) are done.