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

Testnet 56: Callisto #2761

Closed
16 of 17 tasks
conorsch opened this issue Jun 29, 2023 · 1 comment
Closed
16 of 17 tasks

Testnet 56: Callisto #2761

conorsch opened this issue Jun 29, 2023 · 1 comment
Assignees
@aubrika

Comments

@conorsch
Copy link
Contributor

conorsch commented Jun 29, 2023 •
edited by avahowell
Loading

Testnet Release

Testnet name: Callisto
Release date: 2023-07-10
Testnet release manager: @aubrika

Testnet Release Manager Checklist

Preceding Friday (sprint planning day):

  • Create GitHub project column, work with team to populate the milestone with tickets targeted for the release.

Tuesday (or after release of previous testnet):

  • Construct the genesis data for the release: - chore: update chain info for 056-callisto #2762
    • Create new testnet directory with initial genesis allocations for this testnet by running cd testnets && ./new-testnet.sh
      • This genesis data will be used for testnet-preview with a randomized version of the future testnet's chain ID.

Thursday:

  • Check in with team again in a release meeting and update the GitHub milestone to ensure it represents what will make it into the testnet.
  • Draft an announcement for peer review to ensure major changes included are comprehensive.

Following Monday (release day):

  • Verify that testnet-preview.penumbra.zone is operational; it is redeployed on every push to main, and is an exact preview of what is about to be deployed.
  • 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 ~90m, most of which is the macOS builds.
  • 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.
  • You must manually review the Waiting deployment in the GitHub Action UI before the deployment will begin. Monitor the GitHub action to ensure it completes after it is approved.
  • Delegate to the Penumbra Labs CI validators; use amounts of ~200k penumbra per validator.
  • Update the User Guide to mention the newly created git tag.
  • Update Galileo deployment, following docs.
  • Make GitHub release object and include the announcement
  • Make the announcement to Discord! 🎉🎉🎉
conorsch added a commit that referenced this issue Jun 29, 2023
@conorsch
chore: update chain info for 056-callisto
00dbd4e 
Refs #2761.
@conorsch conorsch mentioned this issue Jun 29, 2023
Merged
@conorsch conorsch moved this to Tracking Issues in Testnets Jun 29, 2023
conorsch added a commit that referenced this issue Jun 30, 2023
@conorsch
chore: update chain info for 056-callisto
6bccb96 
Refs #2761.
@conorsch conorsch mentioned this issue Jul 10, 2023
Merged
@conorsch
Copy link
Contributor Author

Shipped https://github.com/penumbra-zone/penumbra/releases/tag/v0.56.0

@github-project-automation github-project-automation bot moved this from Tracking Issues to Testnet 57: Ganymede in Testnets Jul 12, 2023
@conorsch conorsch mentioned this issue Jul 25, 2023
Merged
@conorsch conorsch moved this from Testnet 57: Ganymede to Testnet 56: Callisto in Testnets Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aubrika aubrika

Labels
None yet
Projects
No open projects
Testnets
Status: Testnet 56: Callisto
Milestone
No milestone
Development

No branches or pull requests
2 participants
@conorsch @aubrika