Hi,
1. We might want to explicitly define the meaning of "releases that
are still supported" (mentioned under Release Schedule); for
instance, is it only the current major release, or one or two prior
releases as well? The section on Backwards Compatibility talks about
active and deprecated features at a more granular level, but not the
definition of supported releases.
This may be different with each major release. For example, 1.1 may be
supported but 1.2 might not (say there’s a horrible bug). I will add
language about supported releases and when a release may not be
supported.
I don’t think this should be arbitrary. We need to have a consistent
policy here, that addresses bug fixes and security fixes. If there is a
horrible bug, and it’s a supported release, we should issue a patch.
I think, at least for the next few releases, we want people to be
following the release train pretty closely — so we shouldn’t
maintain support for prior releases, except for security fixes, which
should go 2 releases back. Once we hit our first LTS release, we should
review this policy.
Thoughts?
Sterling
