+1 On Thu, Sep 10, 2020 at 2:26 PM Prashant Sharma <scrapco...@gmail.com> wrote:
> Thanks again, looks like it works now. Please take a look. > > On Thu, Sep 10, 2020 at 11:42 AM Prashant Sharma <scrapco...@gmail.com> > wrote: > >> Hi Wenchen and Sean, >> >> Thanks for looking into this and all the details. >> >> I have now updated the key in those keyservers. Now, how do I refresh >> nexus? >> >> Thanks, >> >> On Thu, Sep 10, 2020 at 9:13 AM Sean Owen <sro...@gmail.com> wrote: >> >>> Yes I can do that and I am sure it's fine, but why has it been visible >>> in the past and not now? Minor thing to fix. >>> >>> On Wed, Sep 9, 2020, 9:09 PM Wenchen Fan <cloud0...@gmail.com> wrote: >>> >>>> Sean, you need to login https://repository.apache.org/ and pick the >>>> staging repo 1361, then check its status, you will see this >>>> [image: image.png] >>>> >>>> On Thu, Sep 10, 2020 at 9:26 AM Mridul Muralidharan <mri...@gmail.com> >>>> wrote: >>>> >>>>> >>>>> I imported our KEYS file locally [1] to validate ... did not use >>>>> external keyserver. >>>>> >>>>> Regards, >>>>> Mridul >>>>> >>>>> [1] wget https://dist.apache.org/repos/dist/dev/spark/KEYS -O - | gpg >>>>> --import >>>>> >>>>> On Wed, Sep 9, 2020 at 8:03 PM Wenchen Fan <cloud0...@gmail.com> >>>>> wrote: >>>>> >>>>>> I checked >>>>>> https://repository.apache.org/content/repositories/orgapachespark-1361/ , >>>>>> it says the Signature Validation failed. >>>>>> >>>>>> Prashant, can you double-check your gpg key and make sure it's >>>>>> uploaded to public key servers like the following? >>>>>> http://pool.sks-keyservers.net:11371 >>>>>> http://keyserver.ubuntu.com:11371 >>>>>> >>>>>> >>>>>> On Wed, Sep 9, 2020 at 6:12 AM Mridul Muralidharan <mri...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> +1 >>>>>>> >>>>>>> Signatures, digests, etc check out fine. >>>>>>> Checked out tag and built/tested with -Pyarn -Phadoop-2.7 -Phive >>>>>>> -Phive-thriftserver -Pmesos -Pkubernetes >>>>>>> >>>>>>> Thanks, >>>>>>> Mridul >>>>>>> >>>>>>> >>>>>>> On Tue, Sep 8, 2020 at 8:55 AM Prashant Sharma <scrapco...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Please vote on releasing the following candidate as Apache Spark >>>>>>>> version 2.4.7. >>>>>>>> >>>>>>>> The vote is open until Sep 11th at 9AM PST and passes if a majority >>>>>>>> +1 PMC votes are cast, with a minimum of 3 +1 votes. >>>>>>>> >>>>>>>> [ ] +1 Release this package as Apache Spark 2.4.7 >>>>>>>> [ ] -1 Do not release this package because ... >>>>>>>> >>>>>>>> To learn more about Apache Spark, please see >>>>>>>> http://spark.apache.org/ >>>>>>>> >>>>>>>> There are currently no issues targeting 2.4.7 (try project = SPARK >>>>>>>> AND "Target Version/s" = "2.4.7" AND status in (Open, Reopened, "In >>>>>>>> Progress")) >>>>>>>> >>>>>>>> The tag to be voted on is v2.4.7-rc3 (commit >>>>>>>> 14211a19f53bd0f413396582c8970e3e0a74281d): >>>>>>>> https://github.com/apache/spark/tree/v2.4.7-rc3 >>>>>>>> >>>>>>>> The release files, including signatures, digests, etc. can be found >>>>>>>> at: >>>>>>>> https://dist.apache.org/repos/dist/dev/spark/v2.4.7-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-1361/ >>>>>>>> >>>>>>>> The documentation corresponding to this release can be found at: >>>>>>>> https://dist.apache.org/repos/dist/dev/spark/v2.4.7-rc3-docs/ >>>>>>>> >>>>>>>> The list of bug fixes going into 2.4.7 can be found at the >>>>>>>> following URL: >>>>>>>> https://s.apache.org/spark-v2.4.7-rc3 >>>>>>>> >>>>>>>> This release is using the release script of the tag v2.4.7-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 an out of date RC going forward). >>>>>>>> >>>>>>>> =========================================== >>>>>>>> What should happen to JIRA tickets still targeting 2.4.7? >>>>>>>> =========================================== >>>>>>>> >>>>>>>> The current list of open tickets targeted at 2.4.7 can be found at: >>>>>>>> https://issues.apache.org/jira/projects/SPARK and search for >>>>>>>> "Target Version/s" = 2.4.7 >>>>>>>> >>>>>>>> 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. >>>>>>>> >>>>>>>
