It probably depends a lot on whether we have volunteers to do the releases too. It sounds like it's probably worth creating a 2.12.0 release in JIRA - we can always bump anything targeted for that release to 3.0 if it doesn't happen.
On Tue, Oct 24, 2017 at 10:52 AM, Lars Volker <l...@cloudera.com> wrote: > I like Jim's idea of having a process to scope out 3.0. > > Tim, can you think of features that are already lined up for 3.0 that we're > currently holding off on? If there are no pressing issues, I think it'd be > great to start working on scoping out 3.0 and produce 2.x releases until > then. > > On Tue, Oct 24, 2017 at 10:19 AM, Jim Apple <jbap...@cloudera.com> wrote: > > > Do we want to have a 3.0 process, where one person tracks all of the open > > breaking-change JIRAs and makes sure nothing gets accidentally left out? > I > > ask this because, if the answer is "yes", we might make the 2.12 decision > > based on scope and quantity of 3.0 JIRAs. > > > > On Tue, Oct 24, 2017 at 10:07 AM, Tim Armstrong <tarmstr...@cloudera.com > > > > wrote: > > > > > I was just retargeting some JIRAs from 2.11 to a later release. I'm > > > wondering if people had thoughts on whether we should have a 2.12 > release > > > before 3.0? > > > > > > We have a lot of breaking changes queued up so I'm sure people are > > looking > > > forward to 3.0, but do we think there will be a minor release before > > then? > > > > > >
