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? >
