I feel like we aren't mature enough yet to formalize this. We only have 1 official "release" under our belt and we are working towards our second. I think the best solution for now would be to try to define this as we go and handle security, regressions, etc with discussions. Of course, I can be convinced otherwise.
On Wed, May 17, 2017 at 3:27 PM, Eric Friedrich (efriedri) < [email protected]> wrote: > Hi All- > We had some discussion around what level of support we want to offer to > users of our software. > > > I'd like to suggest a policy that for all releases we will fix all > security issues and we will fix regressions at discretion of the release > manager. > > There was also discussion about how long we should support a release for. > > Options included: > - Doing only 1-2 LTS releases per year > - Having many smaller point releases with 1 or 2 LTS releases per year. > > We should also define the support timeline of an LTS release to say > supporting the two most recent LTS at all times. > > Thoughts? > >
