We should document the release process in the developer documentation for both minor and patch releases to drive consistency, efficiency, and allow anyone to easily assist in the process. An initial take on the process is discussed here:
https://github.com/airshipit/airshipctl/issues/354#issuecomment-807012049
We could start with the above proposal (with any tweaks necessary) and iterate on it as part of doing each release (especially the first minor (2.0.0) and patch e.g. 2.0.1).
We should document the release process in the developer documentation for both minor and patch releases to drive consistency, efficiency, and allow anyone to easily assist in the process. An initial take on the process is discussed here: https://github.com/airshipit/airshipctl/issues/354#issuecomment-807012049
We could start with the above proposal (with any tweaks necessary) and iterate on it as part of doing each release (especially the first minor (2.0.0) and patch e.g. 2.0.1).