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

Publish next Zebra release: 1.6.0 #7993

Closed
17 tasks
mpguerra opened this issue Nov 24, 2023 · 3 comments · Fixed by #8310, #8309, #8319 or #8315
Closed
17 tasks

Publish next Zebra release: 1.6.0 #7993

mpguerra opened this issue Nov 24, 2023 · 3 comments · Fixed by #8310, #8309, #8319 or #8315
Assignees
Labels
A-release Area: Zebra releases and release management C-trivial Category: A trivial change that is not worth mentioning in the CHANGELOG

Comments

@mpguerra
Copy link
Contributor

Prepare for the Release

These release steps can be done a week before the release, in separate PRs.
They can be skipped for urgent releases.

State Full Sync Test

To check consensus correctness, we want to test that the state format is valid after a full sync. (Format upgrades are tested in CI on each PR.)

State format changes can be made in zebra-state or zebra-chain. The state format can be changed by data that is sent to the state, data created within the state using zebra-chain, or serialization formats in zebra-state or zebra-chain.

After the test has been started, or if it has finished already:

  • Ask for a state code freeze in Slack. The freeze lasts until the release has been published.

Checkpoints

For performance and security, we want to update the Zebra checkpoints in every release.

Missed Dependency Updates

Sometimes dependabot misses some dependency updates, or we accidentally turned them off.

This step can be skipped if there is a large pending dependency upgrade. (For example, shared ECC crates.)

Here's how we make sure we got everything:

  • Run cargo update on the latest main branch, and keep the output
  • If needed, add duplicate dependency exceptions to deny.toml
  • If needed, remove resolved duplicate dependencies from deny.toml
  • Open a separate PR with the changes
  • Add the output of cargo update to that PR as a comment

Prepare and Publish the Release

Follow the steps in the release checklist to prepare the release:

Release PR:

  • Update Changelog
  • Update README
  • Update Zebra Versions
  • Update End of Support Height

Publish Release:

  • Create & Test GitHub Pre-Release
  • Publish GitHub Release
  • Publish Rust Crates
  • Publish Docker Images
@mpguerra mpguerra added P-Medium ⚡ C-trivial Category: A trivial change that is not worth mentioning in the CHANGELOG A-release Area: Zebra releases and release management labels Nov 24, 2023
@mpguerra mpguerra added this to Zebra Nov 24, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Zebra Nov 24, 2023
@upbqdn upbqdn assigned arya2 and upbqdn and unassigned upbqdn and arya2 Nov 24, 2023
@mpguerra mpguerra changed the title Publish next Zebra release: 1.7.0 Publish next Zebra release: 1.6.0 Dec 14, 2023
@mpguerra mpguerra moved this from New to Sprint Backlog in Zebra Jan 29, 2024
This was referenced Feb 21, 2024
@mpguerra mpguerra linked a pull request Feb 22, 2024 that will close this issue
7 tasks
@mpguerra mpguerra moved this from Sprint Backlog to In progress in Zebra Feb 22, 2024
@mpguerra mpguerra linked a pull request Feb 22, 2024 that will close this issue
7 tasks
@oxarbitrage
Copy link
Contributor

@upbqdn can we add to the changelog(and maybe to the readme?) the minimal version of the protoc package needed to build Zebra. I have an older machine and i am getting the error:

error: failed to run custom build command for `zebra-grpc v0.1.0-alpha.1 (/home/oxarbitrage/zebra/pr8303/zebra/zebra-grpc)`

Caused by:
  process didn't exit successfully: `/home/oxarbitrage/zebra/pr8303/zebra/target/debug/build/zebra-grpc-503062e6aec3a443/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=proto/scanner.proto
  cargo:rerun-if-changed=

  --- stderr
  Error: Custom { kind: Other, error: "protoc failed: Unknown flag: --experimental_allow_proto3_optional\n" }

@upbqdn
Copy link
Member

upbqdn commented Feb 22, 2024

Sure, I'll add it there.

@mergify mergify bot closed this as completed in #8309 Feb 22, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Zebra Feb 22, 2024
@upbqdn upbqdn reopened this Feb 22, 2024
@upbqdn
Copy link
Member

upbqdn commented Feb 22, 2024

I opened #8315 instead.

@mpguerra mpguerra moved this from Done to In progress in Zebra Feb 23, 2024
@mpguerra mpguerra linked a pull request Feb 23, 2024 that will close this issue
43 tasks
@mergify mergify bot closed this as completed in #8319 Feb 23, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Zebra Feb 23, 2024
@mpguerra mpguerra linked a pull request Feb 26, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-release Area: Zebra releases and release management C-trivial Category: A trivial change that is not worth mentioning in the CHANGELOG
Projects
Archived in project
4 participants