chore: release checklist

[mudler]

As we are going to release bittensor to the public soon, we want to have a "release pre-flight checklist" that gives us a set of steps to follow in order to have a release.

For instance, an hypothetical checklist can be:

• [ ] Make sure CI tests are passing
• [ ] Check if there are any issue that are blockers to the release
• [ ] Make sure docker images are published correctly
• [ ] Tag the masa-bittensor release
• [ ] Do we have to handle pypi releases?
• [ ] Update the release note text
• [ ] Update the documentation website
• [ ] Update installation instructions if needed https://github.com/masa-finance/masa-bittensor?tab=readme-ov-file#install
• [ ] Ping @giovaroma @lacyg4

Acceptance criteria

• [ ] Define a release checklist, considering the above indications
• [ ] Update the checklist in https://github.com/masa-finance/roadmap/blob/main/.github/ISSUE_TEMPLATE/release-bittensor.md
• [ ] Update the checklist in https://github.com/masa-finance/roadmap/issues/1

[juanmanso]

From my understanding this task is blocked by the following (if true, then we could edit the description to show said blockers):

• Blocked by #85
• Blocked by #111
• Blocked by #109
• [Optional] Blocked by #108

I've put the last one optional since we could go with the realise without static checks as linter for PRs.

[juanmanso]

Regarding functionalities or additional blockers to the release, I'd say that:

• 92

doesn't block the release since the current selection criteria is implemented, we are only making it more performant right now IMO.

[obasilakis]

* Blocked by [Github action to deploy devnet (opentensor subtensor instance with a subnet) #111](https://github.com/masa-finance/masa-bittensor/issues/111)

@juanmanso this isn't a blocker since the users will use the already deployed devnet.

[juanmanso]

• Github action to deploy devnet (opentensor subtensor instance with a subnet) #111

@obasilakis I would agree but afaik the ticket was meant to tackle updates also. It could be avoided if deployment of any updates is handled automatically for the time being

[obasilakis]

• [ ] Restart devnet for clean state
• [ ] Remove local state for:
  • miner
  • validator
  • protocol node
• [ ] Follow instructions in docs/setup to make sure everything is accurate and up-to-date