-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Description
🚢 Estimated shipping date
-
RC1:
2024-06-27 (last confirmed 2024-06-24T18:44:46Z)- 2024-07-01 (updated on 2024-06-28T03:58:09Z - slack thread)
-
RC2:
-
RC3:
-
RC4:
-
RC5:
-
v1.28.0 stable estimated:
2024-07-242024-07-23
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
- chore: NV23 release: backport changes from master #12147
- chore: NV23 backport: one more round of backports from master #12158
- F3 items
- Cherry pick chore: go-state-types: update to RC3 #12154 - backported here
RC2 (current "calibration final-candidate")
- Calibration network genesis should have a faucet account for tokens and datacap #12165 (CONFIRMED TO WORK ON BUTTERFLY)
- Butterfly network genesis should have a faucet account for tokens and datacap #12160
- feat: api: sanity check the "to" address of outgoing messages #12135
- Set upgrade epoch on Calibration
- Update upgrade warning section to warn about:
This upgrade includes an additional migration to the events database. Node operators running Lotus with events turned on (off by default) may experience some delay in initial start-up as a minor database migration takes place. See [filecoin-project/lotus#12080](https://github.com/filecoin-project/lotus/pull/12080) for full details.
- Backport: fix: rpc: missing re-assignment of baseFee in EthFeeHistory #12177
- Backport: fix: build: Ensure Quicknet is used when spinning up 2k/butterfly networks #12175
- Backport: feat:ec:f3: add env var to disable F3 #12176
- Backport: feat: calib: enable f3 by default #12181
Mainnet Upgrade Release
- Backport everything with the backport label (and then remove the backport labe)
- ~ Lotus sync issue: libp2p v0.34.1 libp2p/go-libp2p#2858 ~ (We have bumped go-libp2p. Will close issue once we have a bit more confidence after people have upgraded)
- Release for Lotus v1.28.0-for-mainnet-upgrade go-f3#386
- Dependency updates
✅ 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 themaster
branch tovX.Y.(Z+1)-dev
(bump from feature release) orvX.(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
- Update Lotus dependencies following chore: docs: Add initial
Update_Dependencies_Lotus.md
#12107 - Set the upgrade epoch for the Calibration network
RC1 Steps
- version string in
build/version.go
needs to be updated to end with '-rcX' (in therelease/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 therelease/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 thereleases
branch. - Tag this merge commit (on the
releases
branch) withvX.Y.Z
- Cut the release here.
- Verify that version string in
Post-Release
- Merge the
releases
branch back intomaster
, ignoring the changes toversion.go
(keep the-dev
version from master). Do NOT delete thereleases
branch when doing so!- Double check that everything in
releases
andrelease/v1.28.0
are in master.
- Double check that everything in
- 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
Assignees
Labels
No labels
Type
Projects
Status
☑️ Done (Archive)