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

Release 0.77.2, via point-release #4545

Closed
13 of 19 tasks
conorsch opened this issue Jun 4, 2024 · 1 comment
Closed
13 of 19 tasks

Release 0.77.2, via point-release #4545

conorsch opened this issue Jun 4, 2024 · 1 comment
Assignees

Comments

@conorsch
Copy link
Contributor

conorsch commented Jun 4, 2024

Tooling release

Testnet name: Testnet 77, penumbra-testnet-deimos-8 (unchanged)
Release date: 2024-06-04/5
Testnet release manager: @conorsch

Testnet Release Manager Checklist

On Testnet 77, we enabled fees #4306, and some things broke. Release 0.77.2 is mostly oriented around resolving breakages, but we'll ship some opportunistic improvements where possible, too.

Testnet Release Manager Checklist

Pre-release:

On release day:

  • Draft an announcement for peer review to ensure changes included are comprehensive.
  • Enable testnet deploy workflow, so that point-release logic will run
  • Bump the version number and push its tag, via cargo-release.
    • Run cargo release minor for a new testnet, or cargo release patch for a bugfix. For the latter, make sure you're on a dedicated release branch.
    • Push the commit and newly generated tag, e.g. v0.51.0, to the remote.
  • Manually trigger container-build workflow, bc deploy workflow is disabled
  • Wait for the "Release" workflow to complete
  • Edit the newly created release object, and add a note summarizing the intent of the release
  • Close faucet (chain halt will make it inoperative anyway)
  • Update Galileo deployment, following docs
  • Make the announcement to Discord! 🎉🎉🎉

Post-release cleanup tasks

  • Ensure faucet is open
@conorsch conorsch self-assigned this Jun 4, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Penumbra Jun 4, 2024
@github-actions github-actions bot added the needs-refinement unclear, incomplete, or stub issue that needs work label Jun 4, 2024
@conorsch conorsch removed the needs-refinement unclear, incomplete, or stub issue that needs work label Jun 4, 2024
conorsch added a commit that referenced this issue Jun 4, 2024
conorsch added a commit that referenced this issue Jun 4, 2024
conorsch added a commit that referenced this issue Jun 4, 2024
conorsch added a commit that referenced this issue Jun 4, 2024
I want to keep the docs up to date, and sometimes that requires fussy
management of version numbers, particularly as we invest in multi-branch
workflows to support point releases (e.g. #4545). If *only* the docs
changed, skip the long-running rust tests, because we don't need to
validate rust functionality on docs changes.
conorsch added a commit that referenced this issue Jun 4, 2024
I want to keep the docs up to date, and sometimes that requires fussy
management of version numbers, particularly as we invest in multi-branch
workflows to support point releases (e.g. #4545). If *only* the docs
changed, skip the long-running rust tests, because we don't need to
validate rust functionality on docs changes.
conorsch added a commit that referenced this issue Jun 4, 2024
@conorsch
Copy link
Contributor Author

conorsch commented Jun 4, 2024

@conorsch conorsch closed this as completed Jun 4, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Penumbra Jun 4, 2024
conorsch added a commit that referenced this issue Jun 5, 2024
I want to keep the docs up to date, and sometimes that requires fussy
management of version numbers, particularly as we invest in multi-branch
workflows to support point releases (e.g. #4545). If *only* the docs
changed, skip the long-running rust tests, because we don't need to
validate rust functionality on docs changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant