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

lotus v1.10.0 #6185

Closed
77 of 80 tasks
jennijuju opened this issue May 4, 2021 · 7 comments
Closed
77 of 80 tasks

lotus v1.10.0 #6185

jennijuju opened this issue May 4, 2021 · 7 comments
Assignees
Labels

Comments

@jennijuju
Copy link
Member

jennijuju commented May 4, 2021

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:

Tracking items for rc3:

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:

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
    • 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
Copy link
Contributor

Fatman13 commented May 14, 2021

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

Is "optional release" a typo?

@ROXtiGerf
Copy link

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

@filecoin-project filecoin-project locked and limited conversation to collaborators May 17, 2021
@BigLep
Copy link
Member

BigLep commented May 28, 2021

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
Copy link
Member

BigLep commented Jun 4, 2021

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

@arajasek
Copy link
Contributor

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

@jennijuju
Copy link
Member Author

@BigLep
Copy link
Member

BigLep commented Jun 24, 2021

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

@BigLep BigLep reopened this Jun 24, 2021
@jennijuju jennijuju unpinned this issue Jun 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants