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 52: Amalthe #2415

Closed
17 tasks done
conorsch opened this issue Apr 25, 2023 · 5 comments
Closed
17 tasks done

Testnet 52: Amalthe #2415

conorsch opened this issue Apr 25, 2023 · 5 comments
Assignees
@erwanor

Comments

@conorsch
Copy link
Contributor

conorsch commented Apr 25, 2023 •
edited
Loading

Testnet Release

Testnet name: Amalthe
Release date: 2023-05-15
Testnet release manager: @erwanor

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):

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
Copy link
Contributor Author

conorsch commented May 8, 2023

Pushed target release date 2023-05-08 -> 2023-05-10, to tackle some changes to the DEX engine.

conorsch added a commit that referenced this issue May 8, 2023
@conorsch
ci: compress genesis file during deployment
d8e2560 
During ramp-up to Testnet 52 (#2415), we opportunistically updated the
Discord allocations, and encountered #1783 again. While we need a
durable solution to that problem, we also want a quick fix, so we turn
to tried-and-true file compression: we gzip the generated json file,
base64 encode it to sideload it into the cluster, then decompress it as
part of the initContainer bootstrapping logic during node creation.
This is a "good enough" solution to buy time for the near future,
ensuring that we can continue to update Discord allocations when we
want. The compression ratio is approximately 3x, which gives us some
headroom.
@conorsch conorsch mentioned this issue May 8, 2023
Merged
conorsch added a commit that referenced this issue May 8, 2023
@conorsch
ci: compress genesis file during deployment
562baab 
During ramp-up to Testnet 52 (#2415), we opportunistically updated the
Discord allocations, and encountered #1783 again. While we need a
durable solution to that problem, we also want a quick fix, so we turn
to tried-and-true file compression: we gzip the generated json file,
base64 encode it to sideload it into the cluster, then decompress it as
part of the initContainer bootstrapping logic during node creation.
This is a "good enough" solution to buy time for the near future,
ensuring that we can continue to update Discord allocations when we
want. The compression ratio is approximately 3x, which gives us some
headroom.
@conorsch
Copy link
Contributor Author

New schedule for release of 52 is 2023-05-15, now that the DEX functionality is stabilizing.

This was referenced May 11, 2023
Merged
Closed
@hdevalence
Copy link
Member

Identifying #2560 as a release blocker.

@hdevalence
Copy link
Member

hdevalence commented May 15, 2023 •
edited
Loading

Looking at the project board, looks like the outstanding issues/PRs are:

@conorsch conorsch mentioned this issue May 15, 2023
Open
@conorsch
Copy link
Contributor Author

Announced this morning!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@erwanor erwanor

Labels
None yet
Projects
No open projects
Testnets
Status: Testnet 52: Amalthe
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hdevalence @conorsch @erwanor