Skip to content

More explicit documentation for release process.

Administrator requested to merge releaseprocess into master

Created by: nicksnyder

We held a retrospective for the 3.0 release and the team unanimously requested that we strive to release more regularly. We did release regularly for most of 2018, but got derailed at the end of the year with our work towards 3.0. This PR is a plan to put us back on the rails.

"Regularly" could be defined in a few different ways (e.g. every third Tuesday of the month), but we have decided to adopt a fixed release date like GitLab.

The engineering question that this documentation aims to answer is "how do we consistently release on the 20th of each month"?

If this proposed documentation doesn't clearly answer that question for you, or if you have concerns about the process being documented, please ask questions or suggest edits that would help clarify.

We will discuss this during team meeting on Monday and I will plan to merge it by 4pm PT on Monday.

Merge request reports