| 1 | <!-- Last updated during [v0.30.0 release](https://github.com/ipfs/kubo/pull/10496) --> |
| 2 | |
| 3 | # Items to do upon creating the release issue |
| 4 | |
| 5 | - [ ] Fill in the Meta section |
| 6 | - [ ] Assign the issue to the release owner and reviewer. |
| 7 | - [ ] Name the issue "Release vX.Y.Z" |
| 8 | - [ ] Set the proper values for X.Y.Z |
| 9 | - [ ] Pin the issue |
| 10 | |
| 11 | <!-- |
| 12 | For each pre-release and final release, copy the [release checklist](docs/RELEASE_CHECKLIST.md) |
| 13 | in a new comment and replace the title with the correct value. Having a single comment per |
| 14 | release candidate and final release provides clarity on what steps have already been run per each |
| 15 | release. |
| 16 | --> |
| 17 | |
| 18 | # Meta |
| 19 | |
| 20 | * Release owner: @who |
| 21 | * Release reviewer: @who |
| 22 | * Expected RC date: week of YYYY-MM-DD |
| 23 | * 🚢 Expected final release date: YYYY-MM-DD |
| 24 | * Release PR: <add link once release PR is created> |
| 25 | * Accompanying PR for improving the release process: ([example](https://github.com/ipfs/kubo/pull/9391)) |
| 26 | * Changelog: https://github.com/ipfs/kubo/blob/master/docs/changelogs/vX.Y.md |
| 27 | |
| 28 | # Items In Scope |
| 29 | |
| 30 | ## Required |
| 31 | |
| 32 | <List of items that MUST be included for the release> |
| 33 | |
| 34 | ## Nice To Have (Optional) |
| 35 | |
| 36 | <List of items that MAY be included for the release> |