Let me start with a version 2+ tag and at least write in the
description that it's only for issues that are clearly to be fixed,
but must wait until 2.x.
On Thu, Feb 12, 2015 at 8:54 AM, Patrick Wendell pwend...@gmail.com wrote:
Yeah my preferred is also having a more open ended 2+ for issues
Yeah my preferred is also having a more open ended 2+ for issues
that are clearly desirable but blocked by compatibility concerns.
What I would really want to avoid is major feature proposals sitting
around in our JIRA and tagged under some 2.X version. IMO JIRA isn't
the place for thoughts about
Patrick and I were chatting about how to handle several issues which
clearly need a fix, and are easy, but can't be implemented until a
next major release like Spark 2.x since it would change APIs.
Examples:
https://issues.apache.org/jira/browse/SPARK-3266
It seems to me having a version that is 2+ is good for that? Once we move
to 2.0, we can retag those that are not going to be fixed in 2.0 as 2.0.1
or 2.1.0 .
On Thu, Feb 12, 2015 at 12:42 AM, Sean Owen so...@cloudera.com wrote:
Patrick and I were chatting about how to handle several issues
