Document the release process #114
Labels
5-Documentation
Requires documentation updates
enhancement
New feature or request
priority/medium
Default priority for items
size m
2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Milestone
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:
airshipit/airshipctl#354 (comment)
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).
The text was updated successfully, but these errors were encountered: