+1 Thanks, Dongjoon.
On Mon, Jun 8, 2020 at 6:37 AM Russell Spitzer <russell.spit...@gmail.com> wrote: > +1 (non-binding) ran the new SCC DSV2 suite and all other tests, no issues > > On Sun, Jun 7, 2020 at 11:12 PM Yin Huai <yh...@databricks.com> wrote: > >> Hello everyone, >> >> I am wondering if it makes more sense to not count Saturday and Sunday. I >> doubt that any serious testing work was done during this past weekend. Can >> we only count business days in the voting process? >> >> Thanks, >> >> Yin >> >> On Sun, Jun 7, 2020 at 3:24 PM Denny Lee <denny.g....@gmail.com> wrote: >> >>> +1 (non-binding) >>> >>> On Sun, Jun 7, 2020 at 3:21 PM Jungtaek Lim < >>> kabhwan.opensou...@gmail.com> wrote: >>> >>>> I'm seeing the effort of including the correctness issue SPARK-28067 >>>> [1] to 3.0.0 via SPARK-31894 [2]. That doesn't seem to be a regression so >>>> technically doesn't block the release, so while it'd be good to weigh its >>>> worth (it requires some SS users to discard the state so might bring less >>>> frightened requiring it in major version upgrade), it looks to be optional >>>> to include SPARK-28067 to 3.0.0. >>>> >>>> Besides, I see all blockers look to be resolved, thanks all for the >>>> amazing efforts! >>>> >>>> +1 (non-binding) if the decision of SPARK-28067 is "later". >>>> >>>> 1. https://issues.apache.org/jira/browse/SPARK-28067 >>>> 2. https://issues.apache.org/jira/browse/SPARK-31894 >>>> >>>> On Mon, Jun 8, 2020 at 5:23 AM Matei Zaharia <matei.zaha...@gmail.com> >>>> wrote: >>>> >>>>> +1 >>>>> >>>>> Matei >>>>> >>>>> On Jun 7, 2020, at 6:53 AM, Maxim Gekk <maxim.g...@databricks.com> >>>>> wrote: >>>>> >>>>> +1 (non-binding) >>>>> >>>>> On Sun, Jun 7, 2020 at 2:34 PM Takeshi Yamamuro <linguin....@gmail.com> >>>>> wrote: >>>>> >>>>>> +1 (non-binding) >>>>>> >>>>>> I don't see any ongoing PR to fix critical bugs in my area. >>>>>> Bests, >>>>>> Takeshi >>>>>> >>>>>> On Sun, Jun 7, 2020 at 7:24 PM Mridul Muralidharan <mri...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> Regards, >>>>>>> Mridul >>>>>>> >>>>>>> On Sat, Jun 6, 2020 at 1:20 PM Reynold Xin <r...@databricks.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Apologies for the mistake. The vote is open till 11:59pm Pacific >>>>>>>> time on Mon June 9th. >>>>>>>> >>>>>>>> On Sat, Jun 6, 2020 at 1:08 PM Reynold Xin <r...@databricks.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Please vote on releasing the following candidate as Apache Spark >>>>>>>>> version 3.0.0. >>>>>>>>> >>>>>>>>> The vote is open until [DUE DAY] and passes if a majority +1 PMC >>>>>>>>> votes are cast, with a minimum of 3 +1 votes. >>>>>>>>> >>>>>>>>> [ ] +1 Release this package as Apache Spark 3.0.0 >>>>>>>>> [ ] -1 Do not release this package because ... >>>>>>>>> >>>>>>>>> To learn more about Apache Spark, please see >>>>>>>>> http://spark.apache.org/ >>>>>>>>> >>>>>>>>> The tag to be voted on is v3.0.0-rc3 (commit >>>>>>>>> 3fdfce3120f307147244e5eaf46d61419a723d50): >>>>>>>>> https://github.com/apache/spark/tree/v3.0.0-rc3 >>>>>>>>> >>>>>>>>> The release files, including signatures, digests, etc. can be >>>>>>>>> found at: >>>>>>>>> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc3-bin/ >>>>>>>>> >>>>>>>>> Signatures used for Spark RCs can be found in this file: >>>>>>>>> https://dist.apache.org/repos/dist/dev/spark/KEYS >>>>>>>>> >>>>>>>>> The staging repository for this release can be found at: >>>>>>>>> >>>>>>>>> https://repository.apache.org/content/repositories/orgapachespark-1350/ >>>>>>>>> >>>>>>>>> The documentation corresponding to this release can be found at: >>>>>>>>> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc3-docs/ >>>>>>>>> >>>>>>>>> The list of bug fixes going into 3.0.0 can be found at the >>>>>>>>> following URL: >>>>>>>>> https://issues.apache.org/jira/projects/SPARK/versions/12339177 >>>>>>>>> >>>>>>>>> This release is using the release script of the tag v3.0.0-rc3. >>>>>>>>> >>>>>>>>> FAQ >>>>>>>>> >>>>>>>>> ========================= >>>>>>>>> How can I help test this release? >>>>>>>>> ========================= >>>>>>>>> >>>>>>>>> If you are a Spark user, you can help us test this release by >>>>>>>>> taking >>>>>>>>> an existing Spark workload and running on this release candidate, >>>>>>>>> then >>>>>>>>> reporting any regressions. >>>>>>>>> >>>>>>>>> If you're working in PySpark you can set up a virtual env and >>>>>>>>> install >>>>>>>>> the current RC and see if anything important breaks, in the >>>>>>>>> Java/Scala >>>>>>>>> you can add the staging repository to your projects resolvers and >>>>>>>>> test >>>>>>>>> with the RC (make sure to clean up the artifact cache before/after >>>>>>>>> so >>>>>>>>> you don't end up building with a out of date RC going forward). >>>>>>>>> >>>>>>>>> =========================================== >>>>>>>>> What should happen to JIRA tickets still targeting 3.0.0? >>>>>>>>> =========================================== >>>>>>>>> >>>>>>>>> The current list of open tickets targeted at 3.0.0 can be found at: >>>>>>>>> https://issues.apache.org/jira/projects/SPARK and search for >>>>>>>>> "Target Version/s" = 3.0.0 >>>>>>>>> >>>>>>>>> Committers should look at those and triage. Extremely important bug >>>>>>>>> fixes, documentation, and API tweaks that impact compatibility >>>>>>>>> should >>>>>>>>> be worked on immediately. Everything else please retarget to an >>>>>>>>> appropriate release. >>>>>>>>> >>>>>>>>> ================== >>>>>>>>> But my bug isn't fixed? >>>>>>>>> ================== >>>>>>>>> >>>>>>>>> In order to make timely releases, we will typically not hold the >>>>>>>>> release unless the bug in question is a regression from the >>>>>>>>> previous >>>>>>>>> release. That being said, if there is something which is a >>>>>>>>> regression >>>>>>>>> that has not been correctly targeted please ping me or a committer >>>>>>>>> to >>>>>>>>> help target the issue. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>> >>>>>> -- >>>>>> --- >>>>>> Takeshi Yamamuro >>>>>> >>>>> >>>>>
