release strategy proposal

Problems to address

Things working well

Proposal 1

This is a WIP. Please feel free to edit if you preserve the spirit, or fork it into a new proposal if you don't.

The philosophy here is to have 1 or more conservatively managed releases but to also always have 1 or more more liberally managed releases where slightly more disruptive things are tolerated. But the latter is neither trunk nor a "development" release.

Some things that characterize a more conservatively managed release:

  1. Establish a litmus test ("rules") for what can go into early maintenance levels of a release
  2. Establish rules for what can go into later maintenance levels of a release
  3. Establish rules for how a major.minor graduates from "early" to "late"
  4. Formally document the above

How this would work over time: