Hi Robert, Thanks for clarifying this so that we all have a common definition of what is a blocker.
The only thing I would disagree, and only is some cases, is the documentation part. I think that in some cases, things that have to do with documentation can and should become blockers. Mainly to motivate devs to take care of them. There are important parts of Flink which are not (sufficiently or at all) documented and this can result in confusion / load in the mailing list / wrong user assumptions. Regards, Kostas > On May 4, 2017, at 7:38 PM, Robert Metzger <rmetz...@apache.org> wrote: > > Hi Flink Devs, > > while checking our JIRA for the 1.3 release, I found that some issues of > type "New Feature" have the priority "Blocker". > With the time-based release model, I don't think its possible to mark a new > feature as a blocker. > > Only a bug that leads to wrong results, system failure or completely > undefined behavior (without any available workaround) is a blocker. > New features, missing documentation or inconveniences are never blockers. > > I understand that people want to express that their feature is so important > that it is basically blocking us from creating a release, but with the > time-based release model, this doesn't really apply. > > If nobody disagrees, I'll un"block" new features to "Major" new features. > > > Regards, > Robert > > > Examples: > https://issues.apache.org/jira/browse/FLINK-6198 > https://issues.apache.org/jira/browse/FLINK-6178 > https://issues.apache.org/jira/browse/FLINK-6163 > https://issues.apache.org/jira/browse/FLINK-6047 > https://issues.apache.org/jira/browse/FLINK-5978 > https://issues.apache.org/jira/browse/FLINK-5968
