Document release process

[angela-tran]

The docs should have notes similar to the steps for Littlepay under Version and Release.

Depends on changes from #86

Acceptance criteria

• There is a new page on the docs site for Releases
• The steps to make a new release are outlined on that page

[indexing]

@angela-tran Maybe we can include this issue in your newly-created milestone to capture improvements to the release process?

[angela-tran]

@indexing The release process for eligibility-api is pretty different from that of benefits and eligibility-server since it's a Python package that gets published to PyPI rather than a web app that runs on Azure, so this project won't be subject to any of the changes in the new milestone.

I could see this issue being a "Stretch" ticket if you think it's worth adding to the Sprint, but I don't think it really belongs in the "Tag-based deployment model" milestone.

[indexing]

@angela-tran Got it. Doesn't seem related to the "Tag-based deployment model" milestone to me either. How urgent is it to have this process documented?

[angela-tran]

@indexing Not urgent right now. It would become more urgent if we were to start some work on eligibility-api but nothing lined up right now