Hopefully today ! I think we can get the release officially out tomorrow. For those of you that don't know, it's already on Maven. Please take a final look at the release notes, as I will turn it into a release page today.
On Wed, Jun 17, 2020 at 11:31 AM, Tom Graves < tgraves...@yahoo.com > wrote: > > Reynold, > > > What's the plan on pushing the official release binaries and source tar? > It would be nice to have the release artifacts now that it's available on > maven. > > > thanks, > Tom > > > On Monday, June 15, 2020, 01:52:12 PM CDT, Reynold Xin < rxin@ databricks. > com ( r...@databricks.com ) > wrote: > > > > > Thanks for the reminder, Dongjoon. > > > > I created the official release tag the past weekend and been working on > the release notes (a lot of interesting changes!). I've created a google > docs so it's easier for everybody to give comment on things that I've > missed: https:/ / docs. google. com/ document/ d/ > 1NrTqxf2f39AXDF8VTIch6kwD8VKPaIlLW1QvuqEcwR4/ > edit ( > https://docs.google.com/document/d/1NrTqxf2f39AXDF8VTIch6kwD8VKPaIlLW1QvuqEcwR4/edit > ) > > > > Plan to publish to maven et al today or tomorrow and give a day or two for > dev@ to comment on the release notes before finalizing. > > > > PS: There are two critical problems I've seen with the release (Spark UI > is virtually unusable in some cases, and streaming issues). I will > highlight them in the release notes and link to the JIRA tickets. But I > think we should make 3.0.1 ASAP to follow up. > > > > > > > On Sun, Jun 14, 2020 at 11:46 AM, Dongjoon Hyun < dongjoon. hyun@ gmail. com > ( dongjoon.h...@gmail.com ) > wrote: > >> Hi, Reynold. >> >> >> Is there any progress on 3.0.0 release since the vote was finalized 5 days >> ago? >> >> >> Apparently, tag `v3.0.0` is not created yet, the binary and docs are still >> sitting on the voting location, Maven Central doesn't have it, and >> PySpark/SparkR uploading is not started yet. >> >> >> https:/ / dist. apache. org/ repos/ dist/ dev/ spark/ v3. 0. 0-rc3-bin/ ( >> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc3-bin/ ) >> >> https:/ / dist. apache. org/ repos/ dist/ dev/ spark/ v3. 0. 0-rc3-docs/ ( >> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc3-docs/ ) >> >> >> >> Like Apache Spark 2.0.1 had 316 fixes after 2.0.0, we already have 35 >> patches on top of `v3.0.0-rc3` and are expecting more. >> >> >> Although we can have Apache Spark 3.0.1 very soon before Spark+AI Summit, >> Apache Spark 3.0.0 should be available in Apache Spark distribution >> channel because it passed the vote. >> >> >> >> Apache Spark 3.0.0 release itself helps the community use 3.0-line >> codebase and makes the codebase healthy. >> >> >> Please let us know if you need any help from the community for 3.0.0 >> release. >> >> >> Thanks, >> Dongjoon. >> >> >> >> On Tue, Jun 9, 2020 at 9:41 PM Matei Zaharia < matei. zaharia@ gmail. com ( >> matei.zaha...@gmail.com ) > wrote: >> >> >>> Congrats! Excited to see the release posted soon. >>> >>> >>>> On Jun 9, 2020, at 6:39 PM, Reynold Xin < rxin@ databricks. com ( >>>> r...@databricks.com ) > wrote: >>>> >>>> >>> >>> >>> >>>> >>>> I waited another day to account for the weekend. This vote passes with the >>>> following +1 votes and no -1 votes! >>>> >>>> >>>> >>>> I'll start the release prep later this week. >>>> >>>> >>>> >>>> +1: >>>> >>>> Reynold Xin (binding) >>>> >>>> Prashant Sharma (binding) >>>> >>>> Gengliang Wang >>>> >>>> Sean Owen (binding) >>>> >>>> Mridul Muralidharan (binding) >>>> >>>> Takeshi Yamamuro >>>> >>>> Maxim Gekk >>>> >>>> Matei Zaharia (binding) >>>> >>>> Jungtaek Lim >>>> >>>> Denny Lee >>>> >>>> Russell Spitzer >>>> >>>> Dongjoon Hyun (binding) >>>> >>>> DB Tsai (binding) >>>> >>>> Michael Armbrust (binding) >>>> >>>> Tom Graves (binding) >>>> >>>> Bryan Cutler >>>> >>>> Huaxin Gao >>>> >>>> Jiaxin Shan >>>> >>>> Xingbo Jiang >>>> >>>> Xiao Li (binding) >>>> >>>> Hyukjin Kwon (binding) >>>> >>>> Kent Yao >>>> >>>> Wenchen Fan (binding) >>>> >>>> Shixiong Zhu (binding) >>>> >>>> Burak Yavuz >>>> >>>> Tathagata Das (binding) >>>> >>>> Ryan Blue >>>> >>>> >>>> >>>> -1: None >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Sat, Jun 06, 2020 at 1:08 PM, Reynold Xin < rxin@ databricks. com ( >>>> 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/ >>>>> ( >>>>> 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 ( >>>>> 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/ ( >>>>> 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 ( >>>>> 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/ >>>>> ( 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/ ( >>>>> 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 ( >>>>> 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 ( >>>>> 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. >>>>> >>>> >>>> >>> >>> >> >> > >
smime.p7s
Description: S/MIME Cryptographic Signature
