Here are my replies, Sean.
> Since we're here, fine: I vote -1, simply because this states no reason
for the action at all.
Thank you for your explicit vote because
this vote was explicitly triggered by this controversial comment,
"I do not see some police action from the PMC must follow".
> I
Since the genie is out of the bottle now and I have been involved in this
discussion all the way, I think the question ought to be "Apache Spark DEV
community asks Databricks to differentiate its Spark version string". That
makes more sense as Spark DEV community is a superset of PMC if I am not
On Fri, Jun 16, 2023 at 3:58 PM Dongjoon Hyun
wrote:
> I started the thread about already publicly visible version issues
> according to the ASF PMC communication guideline. It's no confidential,
> personal, or security-related stuff. Are you insisting this is confidential?
>
Discussion about a
For the following,
> this discussion should have been on private@ to begin with, but, the ship
has sailed. ...
> This doesn't make sense here.
I started the thread about already publicly visible version issues
according to the ASF PMC communication guideline. It's no confidential,
personal, or
As we noted in the last thread, this discussion should have been on private@
to begin with, but, the ship has sailed.
You are suggesting that non-PMC members vote on whether the PMC has to do
something? No, that's not how anything works here.
It's certainly the PMC that decides what to put in the
No, this is a vote on dev@ intentionally as a part of our previous thread,
"ASF policy violation and Scala version issues" (
https://lists.apache.org/thread/k7gr65wt0fwtldc7hp7bd0vkg1k93rrb)
> did you mean this for the PMC list?
I clearly started the thread with the following.
> - Apache Spark
What does a vote on dev@ mean? did you mean this for the PMC list?
Dongjoon - this offers no rationale about "why". The more relevant thread
begins here:
https://lists.apache.org/thread/k7gr65wt0fwtldc7hp7bd0vkg1k93rrb but it
likewise never got to connecting a specific observation to policy.
+1
Dongjoon
On 2023/06/16 19:53:03 Dongjoon Hyun wrote:
> Please vote on the following statement. The vote is open until June 23th
> 1AM (PST) and passes if a majority +1 PMC votes are cast, with a minimum of
> 3 +1 votes.
>
> Apache Spark PMC asks Databricks to differentiate its Spark
>
Please vote on the following statement. The vote is open until June 23th
1AM (PST) and passes if a majority +1 PMC votes are cast, with a minimum of
3 +1 votes.
Apache Spark PMC asks Databricks to differentiate its Spark
version string to avoid confusions because Apache Spark PMC
is responsible
I want to add two updates on this thread.
First, Ammonite library issue is resolved for Scala 2.12/2.13. For Scala 3, we
can talk later in the scope of Spark 4.
SPARK-44041 Upgrade Ammonite to 2.5.9
This unblocked the following and we start to evaluate them.
SPARK-43832 Upgrade Scala
This was a part of the following on-going discussions.
2023-05-28 Apache Spark 3.5.0 Expectations (?)
https://lists.apache.org/thread/3x6dh17bmy20n3frtt3crgxjydnxh2o0
2023-05-30 Apache Spark 4.0 Timeframe?
https://lists.apache.org/thread/xhkgj60j361gdpywoxxz7qspp2w80ry6
2023-06-05 ASF policy
The vote passes with 6 +1s (4 binding +1s), one -0, and one -1.
Thank you all for your participation and
especially your additional comments during this voting,
Mridul, Hyukjin, and Jungtaek.
(* = binding)
+1:
- Dongjoon Hyun *
- Huaxin Gao *
- Liang-Chi Hsieh *
- Kazuyuki Tanimura
- Chao Sun *
-
Thank you everyone.
I appreciate all your input and conclude this vote.
Dongjoon
On Thu, Jun 15, 2023 at 9:41 AM Hyukjin Kwon wrote:
> I am supportive of setting the timeline for Spark 4.0, and I think it has
> to be done soon.
> If my understanding is correct, we better need to set up the
Hi All,
(This email goes out to all our user and dev project mailing lists, so you
may receive this
email more than once.)
The Travel Assistance Committee has opened up applications to help get
people to the following events:
*Community Over Code Asia 2023 - *
*August 18th to August 20th in
14 matches
Mail list logo
