-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Is "optional release" a typo? |
does all the box need to be ticked to finish this release? |
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. |
I specified in the description above what tasks we're waiting on before rc2 and rc3. |
There will be no RC7, since no real code changes have landed since RC6. |
Per 2021-06-24 standup, reopening until we have gone through and confirmed that all the items (including post release items) are done. |
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:
release/vX.Y.Z
) frommaster
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.scripts/mkreleaselog
, and add it toCHANGELOG.md
version.go
in themaster
branch tovX.(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:
build/version.go
has been updated (in therelease/vX.Y.Z
branch).vX.Y.Z-rcN
Testing an RC:
Stage 0 - Automated Testing
Stage 1 - Internal Testing
Stage 2 - Community Testing
Stage 3 - Community Prod Testing
Create a discussion for this release
when tagging for the major rcs(new features, hot-fixes) releaseStage 4 - Release
version.go
has been updated.release-vX.Y.Z
into thereleases
branch.releases
branch) withvX.Y.Z
Create a discussion for this release
when tagging the releasePost-Release
releases
branch back intomaster
, ignoring the changes toversion.go
(keep the-dev
version from master). Do NOT delete thereleases
branch when doing so!❤️ Contributors
💙Thank you to all the contributors!
Leave a comment here if you have any questions.
The text was updated successfully, but these errors were encountered: