On Fri, Apr 3, 2020 at 12:31 AM Sean Owen wrote:
> On Wed, Apr 1, 2020 at 10:28 PM Jungtaek Lim
> wrote:
> > The definition of "latest version" would matter, especially there's a
> time we prepare minor+ version release.
> >
> > For example, lots of people (even including committers) filed an
>
On Wed, Apr 1, 2020 at 10:28 PM Jungtaek Lim
wrote:
> The definition of "latest version" would matter, especially there's a time we
> prepare minor+ version release.
>
> For example, lots of people (even including committers) filed an
> "improvement" issue with setting fix version to 3.0, which
I didn't point out actual case "intentionally", because I want to avoid
unnecessary debate and make sure we don't decide with bias. Note that the
context would include people.
I have been seen these requests consistently (at least consistently for 1,
but I feel I also saw 2 more than couple of tim
Probably the discussion here about Improvement Jira tickets and the
"Affects Version" field:
https://github.com/apache/spark/pull/27534#issuecomment-588416416
On Wed, Apr 1, 2020 at 9:59 PM Hyukjin Kwon wrote:
> > 2) check with older versions to fill up affects version for bug
> I don't agree wi
> 2) check with older versions to fill up affects version for bug
I don't agree with this in general. To me usually it's "For the type of
bug, assign one valid version" instead.
> The only place where I can see some amount of investigation being
required would be for security issues or correctness
I agree with what Sean detailed.
The only place where I can see some amount of investigation being required
would be for security issues or correctness issues.
Knowing the affected versions, particularly if an earlier supported version
does not have the bug, will help users understand the broken/in
I think we discussed this briefly on a PR.
It's not as clear what it means for an Improvement to 'affect a
version'. Certainly, an improvement to a feature introduced in 1.2.3
can't affect anything earlier, and implicitly affects everything
after. It's not wrong to say it affects the latest versio
Hi devs,
I know we're busy with making Spark 3.0 be out, but I think the topic is
good to discuss at any time and actually be better to be resolved sooner
than later.
In the page "Contributing to Spark", we describe the guide of "affects
version" as "For Bugs, assign at least one version that is
