Closed rootulp closed 1 month ago
moving this to no status since the team has not prioritized it for the upcoming sprint. currently, the automation adds everything to todo but before we change it let's try and keep new issues in no status 🙏🏻
From a sync call we want this for future >= v2.x.x releases too. It should include:
Context
Spun out from https://github.com/celestiaorg/celestia-app/issues/2810
Problem
Currently there are manual tests that we want to perform before cutting future v1.x releases. These release blocking steps aren't documented or common understanding amongst the team.
Proposal
Draft a release guide that includes a checklist for steps that must be performed before cutting future v1.x releases. Example: