-
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 Node and Miner Release v1.31.0 (nv24++) #12344
Comments
The issue description was updated to make clear that this will be a parallel release to v1.30.0 and that it will include functionality beyond what is required for nv24. |
@rjan90 : FYI I populated the release issue with the template. |
|
Thanks for catching the things I missed, and updating this issue 🙏
We decided to do a lotus-miner release as well release to allow thorough testing of PR #12690. This PR modifies the mining loop, which is considered highly sensitive code and requires careful validation. |
The stable releases of v1.31.0 has been published here: |
Closing as the stable release of v1.31.0 has been released |
Note
This release is nv24++ meaning it will have the minimum functionality needed for nv24 (i.e., what is in v1.30.0), but also some additional functionality that is higher risk that we don't want to obligate users to upgrade to during a network upgrade.
😶🌫 Meta
🚢 Estimated shipping date
🪢 Dependencies for releases
Note
master
.Release Checklist
.rc1
Stable (non-RC)
lotus-shed datastore import
#12695✅ Release Checklist
Before RC1
docs(release): v1.31.0 release template improvements
for improving future releases.Post Release
step.release/v1.31.0
orrelease/miner/v1.31.0
) frommaster
and make any further release-related changes to this branch.master
branch Version string updatesbuild/version.go
tov1.31.1-dev
.NodeBuildVersion
), a miner release (MinerBuildVersion
), or both.make gen && make docsgen-cli
before committing changes.UNRELEASED
section header toUNRELEASED v1.31.0
UNRELEASED v1.31.0
section's content to be "See https://github.com/filecoin-project/lotus/blob/release/v1.31.0/CHANGELOG.md"UNRELEASED
header to top.build: update Lotus Node version to v1.31.1-dev in master
RCs
rc1
Important
These PRs should be done in and target the
release/v1.31.0
orrelease/miner/v1.31.0
branch.Backport PR
Dependencies for releases
have landedbuild: backport changes for node v1.31.0-rc1
Release PR
build/version.go
to one ending with '-rc1'.NodeBuildVersion
), a miner release (MinerBuildVersion
), or both.make gen && make docsgen-cli
to generate documentationbuild: release Lotus node v1.31.0-rc1
git log --oneline --graph vA.B.C..
, where A.B.C correspond to the previous release.gh
cli command looking at merged PRs into master and sorted by title to group similar areas (whereYYYY-MM-DD
is the start search date):gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
🚢 Estimated shipping date
tableTesting
Note
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.
Stable (non-RC) Release
Important
These PRs should be done in and target the
release/v1.31.0
orrelease/miner/v1.31.0
branch.Backport PR
Dependencies for releases
have landedbuild: backport changes for node v1.31.0
release/v1.31.0
branch #12721Release PR
build/version.go
to one NOT ending with '-rc1'.NodeBuildVersion
), a miner release (MinerBuildVersion
), or both.make gen && make docsgen-cli
to generate documentationbuild: release Lotus node v1.31.0
git log --oneline --graph vA.B.C..
, where A.B.C correspond to the previous release.gh
cli command looking at merged PRs into master and sorted by title to group similar areas (whereYYYY-MM-DD
is the start search date):gh pr list --repo filecoin-project/lotus --search "base:master merged:>YYYY-MM-DD" --json number,mergedAt,author,title | jq -r '.[] | [.number, .mergedAt, .author.login, .title] | @tsv' | sort -k4
🚢 Estimated shipping date
tableTesting
Note
Link to any special steps for testing releases beyond ensuring CI is green. Steps can be inlined here or tracked elsewhere.
Post-Release
master
cherry-picking the CHANGELOG commits from therelease/v1.31.0
branch. Title itchore(release): cherry-pick v1.31.0 changelog back to master
master
first before backporting to the release branch, the only changes should be CHANGELOG updates.Before RC1
with any improvements determined from this latest release iteration.❤️ Contributors
See the final release notes!
Leave a comment in this ticket!
The text was updated successfully, but these errors were encountered: