Skip to content

[WIP] Lotus Release v1.28.0 #12109

@rjan90

Description

@rjan90

🚢 Estimated shipping date

Dependencies for releases

This is the set of changes that need to make it a given RC. This is effectively the set of changes to cherry-pick from master.

RC1

RC2 (current "calibration final-candidate")

Mainnet Upgrade Release

✅ Release Checklist

  • Wait for the v1.27.1 release to complete: [Shipped] Lotus Client Release v1.27.1 #12073
  • Fork a new branch (release/v1.28.0) from master.
    • Any further release related changes need to be made in this branch or cherry-picked to it.
    • If any "non-trivial" changes get added to the release, uncheck all the checkboxes and return to this stage.
  • (After the RC gets cut) Bump the version in build/version.go in the master branch to vX.Y.(Z+1)-dev (bump from feature release) or vX.(Y+1).0-dev (bump from mandatory release). Run make gen and make docsgen-cli before committing changes
    chore: bump version in master #12074

Prepping an RC

RC prep steps for network upgrade for Calibration

RC1 Steps

  • version string in build/version.go needs to be updated to end with '-rcX' (in the release/vX.Y.Z branch)
  • run make gen && make docsgen-cli
  • Changelog prep
    • Generate changelog using the script at scripts/mkreleaselog
    • Add contents of generated text to lotus/CHANGELOG.md
    • Editorializing (FIPs, actor bundles, new feature callouts - example)
  • Commit using PR: chore: release: Lotus v1.28.0-rc1 #12169
  • tag commit with vX.Y.Z-rcN
  • cut a pre-release here

We've cut the first RC using these steps at https://github.com/filecoin-project/lotus/releases/tag/v1.28.0-rc1.

RC2 Steps

  • version string in build/version.go needs to be updated to end with '-rcX' (in the release/vX.Y.Z branch)
  • run make gen && make docsgen-cli
  • Changelog prep
    • Generate changelog using the script at scripts/mkreleaselog
    • Add contents of generated text to lotus/CHANGELOG.md
    • Editorializing (FIPs, actor bundles, new feature callouts - example)
  • Commit using PR
  • tag commit with vX.Y.Z-rcN
  • cut a pre-release here

Stable Release

  • Final preparation
    • Verify that version string in version.go has been updated.
    • Verify that codegen is up to date (make gen && make docsgen-cli)
    • Ensure that CHANGELOG.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.

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!
    • Double check that everything in releases and release/v1.28.0 are in 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.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status

☑️ Done (Archive)

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions