Testnet #42: Adraste

[conorsch]

Testnet Release

Testnet name: Adraste
Release date: 2023-01-30
Testnet release manager: @conorsch

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: Prep for 042-testnet #1878
  • 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.
• Create new git tag e.g. 006-orthosie on main (tags created on any other branches will not transfer when merged in) and push to shared remote: git tag -a <tag_name> - must be annotated tag, i.e. git tag -a for Vergen build. This will create a Waiting GitHub Action for deployment.
• 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.
• Update the User Guide to mention the newly created git tag.
• Delegate to the Penumbra Labs CI validator
• Make GitHub release object and include the announcement
• Make the announcement to Discord! 🎉🎉🎉

[conorsch]

Release is live! Galileo is down, tracked in penumbra-zone/galileo#24 ; will follow up with that and the post-release tasks tracked above.

[conorsch]

Galileo working as of penumbra-zone/galileo@a550a3c, closing.