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.

Sign up for GitHub

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

Jump to bottom

Release Testnet 75, deimos-8, via chain reset #4374

Closed
18 of 21 tasks
conorsch opened this issue May 10, 2024 · 3 comments · Fixed by #4390
Closed
18 of 21 tasks

Release Testnet 75, deimos-8, via chain reset #4374

conorsch opened this issue May 10, 2024 · 3 comments · Fixed by #4390
Assignees
@conorsch

Comments

@conorsch
Copy link
Contributor

conorsch commented May 10, 2024 •
edited
Loading

Testnet Release

Testnet name: Testnet 75, penumbra-testnet-deimos-8, via chain reset
Release date: 2024-05-10
Testnet release manager: @conorsch

Testnet Release Manager Checklist

We intend to ship a reset, to recover from the mismanaged upgrade to 74. See #4325 and #4373 for details.

Pre-release:

  • Fetch funding streams from previously active validators
  • Prepare release PR that makes the following changes:

On release day:

  • Draft an announcement for peer review to ensure major changes included are comprehensive.
  • Enable testnet deploy workflow, so that chain is reset
  • 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.
  • Wait for the "Release" workflow to complete: it'll take ~60m, most of which is the Windows builds.
  • You must manually review the waiting deployment
  • Delegate to the Penumbra Labs CI validators; use amounts of ~200k penumbra per validator.
  • Open a position to provide some initial liquidity: pcli tx lp replicate xyk penumbra:test_usd 20000penumbra --current-price 20
  • Edit the newly created (and published) release object, then click "Generate release notes." Cut and paste the generated text from the bottom to the top of the post, then save it.
  • Close faucet (chain halt will make it inoperative anyway)
  • Update Galileo deployment, following docs.
  • Make the announcement to Discord! 🎉🎉🎉

Post-release cleanup tasks

  • Send funds to funding streams for prior chain's validators, to help them get active again
  • Ensure faucet is open
  • Perform Hermes maintenance to get relayer running again
  • Update GH templates for:
    • release planning (this template was heavily revised and can be reused)
    • PR templates to ask for test plans
@conorsch conorsch self-assigned this May 10, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Penumbra May 10, 2024
@github-actions github-actions bot added the needs-refinement unclear, incomplete, or stub issue that needs work label May 10, 2024
@conorsch conorsch changed the title Release Testnet 75, deimos-7, via chain reset Release Testnet 75, deimos-8, via chain reset May 10, 2024
@cratelyn cratelyn removed the needs-refinement unclear, incomplete, or stub issue that needs work label May 10, 2024
conorsch added a commit that referenced this issue May 10, 2024
@conorsch
chore: prepare testnet 75
eb5836a 
Makes three substantive changes:

  * resets `TOTAL_HALT_COUNT` to 0
  * increments `APP_VERSION`
  * increments chain_id `penumbra-testnet-deimos-7` ->
    `penumbra-testnet-deimos-8`

There are multiple chain id directories included, pulled from the
`release/v0.73.2` tag. Due to our multi-branch workflow, we never
backported those testnet configs to the main branch, but doing so
is necessary now that we're releasing from main again.

Refs #4374.
This was referenced May 10, 2024
Merged
Closed
conorsch added a commit that referenced this issue May 10, 2024
@conorsch
chore: prepare testnet 75
0f34970 
Makes three substantive changes:

  * resets `TOTAL_HALT_COUNT` to 0
  * increments `APP_VERSION`
  * increments chain_id `penumbra-testnet-deimos-7` ->
    `penumbra-testnet-deimos-8`

There are multiple chain id directories included, pulled from the
`release/v0.73.2` tag. Due to our multi-branch workflow, we never
backported those testnet configs to the main branch, but doing so
is necessary now that we're releasing from main again.

Refs #4374.
@conorsch conorsch moved this from Backlog to In progress in Penumbra May 10, 2024
@conorsch conorsch mentioned this issue May 10, 2024
Merged
1 task
@conorsch
Copy link
Contributor Author

Confirmed IBC outbound (Penumbra -> Osmosis) on Testnet 75:

However, given the problems documented in #4310, I expect that channel will close soon.

@conorsch conorsch mentioned this issue May 10, 2024
Merged
@conorsch
Copy link
Contributor Author

Confirmed IBC inbound (Osmosis -> Penumbra) on Testnet 75:

This was referenced May 14, 2024
Merged
Merged
@hdevalence
Copy link
Member

This is done, correct?

@github-project-automation github-project-automation bot moved this from In progress to Done in Penumbra May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@conorsch conorsch

Labels
None yet
Projects
Penumbra
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: add upgrade planning checklist penumbra-zone/penumbra
3 participants
@hdevalence @conorsch @cratelyn