This has been ongoing for a week, the vote has been open for 3 days,
Dongjoon has replied today (not sure if you saw it), and I think this is
all around in circles; I don't see any basis for waiting 24 hours (? where
is this from?) I don't know if this is a code change vote - there is no
code changing. But if it were, I think everyone's still missing the
technical justification part, so, same result. I think this is definitely
the correct result by spirit and letter of policy.

It's not like we can't all change minds if some new legitimate concern or
angle comes out, but, I'd say it's better not to keep entertaining this
conversation if there is no movement on the substance of the discussion.
There is just clear support for the position in this vote.



On Thu, Mar 13, 2025 at 9:42 PM Mark Hamstra <markhams...@gmail.com> wrote:

> This vote has not passed.
>
> The proposed code change has been vetoed by a qualified voter. The
> validity of that veto has been called into question since "the voter
> must provide with the veto a technical justification showing why the
> change is bad (opens a security exposure, negatively affects
> performance, etc. )." It has been less than 24 hours since Dongjoon's
> veto was called into question. He should be given a chance to explain
> why there is technical justification for it.
>
> On Thu, Mar 13, 2025 at 7:21 PM Jungtaek Lim
> <kabhwan.opensou...@gmail.com> wrote:
> >
> > The vote passes with 7 +1s (3 binding +1s) and 1 -1s (1 binding -1s).
> > Thanks to all who helped with the vote!
> >
> > I'm going to make a code change in branch-4.0 quickly so that we don't
> have to trigger another RC for Spark 4.0.0 just because of this.
> >
> > (* = binding)
> > +1:
> > - Sean R. Owen *
> > - Jungtaek Lim
> > - Nicholas Chammas
> > - Wenchen Fan *
> > - Adam Binford
> > - Russell Jurney
> > - Yang Jie *
> >
> > -1:
> > - Dongjoon Hyun *
> >
> > Thanks,
> > Jungtaek Lim (HeartSaVioR)
>
> ---------------------------------------------------------------------
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
>

Reply via email to