diff --git a/.github/ISSUE_TEMPLATE/point_release.md b/.github/ISSUE_TEMPLATE/point_release.md new file mode 100644 index 0000000000..dcb6aae726 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/point_release.md @@ -0,0 +1,30 @@ +--- +name: Point release +about: Checklist for preparing a point release for tooling +title: Release vX.Y.Z, via point-release +labels: '' +assignees: '' +--- + +# Tooling Release + + +In order to ship some minor improvements and bug fixes, let's prepare a `vX.Y.Z.` release, flushing out the current contents of the main branch. + +## Changes to include + + +- [ ] Everything on current main +- [ ] Feature foo in PR: +- [ ] Feature bar in PR: + +## Compatibility +As this is a point-release, all changes must be fully compatible for all nodes and clients. +Careful attention should be given to the delta between most recent tag on the main branch: +https://github.com/penumbra-zone/penumbra/compare/v(X.Y.(Z-1)..main diff --git a/.github/ISSUE_TEMPLATE/release_testnet.md b/.github/ISSUE_TEMPLATE/release_testnet.md deleted file mode 100644 index d27ec313fb..0000000000 --- a/.github/ISSUE_TEMPLATE/release_testnet.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -name: Testnet release -about: Checklist for releasing a testnet -title: '' -labels: '' -assignees: '' - ---- - -# Testnet Release - -Testnet name: X -Release date: X -Testnet release manager: X - -# 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: - - [ ] 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](https://crates.io/crates/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](https://github.com/penumbra-zone/penumbra/actions/workflows/release.yml) to complete: it'll take ~60m, most of which is the Windows 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](https://docs.github.com/en/actions/managing-workflow-runs/reviewing-deployments) the [`Waiting` deployment in the GitHub Actions UI](https://github.com/penumbra-zone/penumbra/actions/workflows/deploy-testnet.yml) 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. -- [ ] Open a position to provide some initial liquidity: `pcli tx lp replicate xyk penumbra:test_usd 20000penumbra --current-price 20` -- [ ] Update Galileo deployment, [following docs](https://github.com/penumbra-zone/galileo). -- [ ] Update Osiris deployment, [following docs](https://github.com/penumbra-zone/osiris). -- [ ] Make the announcement to Discord! 🎉🎉🎉