Difference between revisions of "Release Process Debrief"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
As ideas gel into actionable tasks they can be moved off this page into bug trackers or todo lists. | As ideas gel into actionable tasks they can be moved off this page into bug trackers or todo lists. | ||
== Development == | |||
== Scheduling == | == Scheduling == | ||
Revision as of 23:35, 9 August 2017
Release Process Debrief
This is for capturing braindumps and random observations/ideas on streamlining and improving our release processes.
As ideas gel into actionable tasks they can be moved off this page into bug trackers or todo lists.
Development
Scheduling
- 0.92.2 had just one pre-release, but given the switch to git and the introduction of the releases app, it may have been beneficial to do one or two more pre-releases.
- Objectively we're getting better at establishing and following a schedule, but for 0.92.2 there was still delays at the end. In each of 0.92.0, 0.92.1, and 0.92.2 the delays were caused by unique causes; *something* always piles up at the end and it's difficult to predict what it'll be.