cairo-contracts
cairo-contracts copied to clipboard
Automate milestone changes after release
🧐 Motivation Everytime there's a relese, the milestones need to be adjusted in order to accomodate the new cycle. The way it's done today:
- Delete current milestone
- Change the name of the other milestones(next -> current and after -> next)
- Create a new milestone named after
This can probably be automated via GH actions and can be run manually after every major release.
@andrew-fleming This is the process correct?
This is the process correct?
It can get weird with the milestone numbers that way. I also really don't like changing the name to bump. I do it like this:
- In the kanban, archive all issues in "Resolved"
- In the "Next" tab, change the "next" milestone in each issue to "current"
- Do the same with "After" to "Next"
- Go through backlog and add new issues to "After"
IMO this is less error prone since we're only changing the status of the issues through the dropdown menu