I agree with Wenchen.

I can volunteer for Apache Spark 3.1.2 release manager at least.

Bests,
Dongjoon.


On Wed, Apr 28, 2021 at 10:15 AM Wenchen Fan <cloud0...@gmail.com> wrote:

> Shall we make new releases for 3.0 and 3.1? So that people don't need to
> change the sbt resolver/pom files to work around Bintray sunset. It's also
> been a while since the last 3.0 and 3.1 releases.
>
> On Tue, Apr 27, 2021 at 9:02 AM Matthew Powers <
> matthewkevinpow...@gmail.com> wrote:
>
>> Great job fixing this!!  I just checked and it's working on my end.  Updated
>> the resolver
>> <https://github.com/MrPowers/spark-bulba/commit/887791f1106e3f6f707d2176f12edf093d4334a5>
>> and sbt test still works just fine.
>>
>> On Mon, Apr 26, 2021 at 3:31 AM Bo Zhang <bo.zh...@databricks.com> wrote:
>>
>>> Hi Apache Spark devs,
>>>
>>> As you might know, Bintray, which is the repository service used for
>>> spark-packages.org, is in its sunset process. There was a planned
>>> brown-out on April 12th
>>> <https://status.bintray.com/incidents/4mzph0y8l6hk> and there will be
>>> another one on April 26th
>>> <https://status.bintray.com/incidents/x1dvhtdqkcnx>, and it will no
>>> longer be available from May 1st.
>>>
>>> We have spun up a new repository service at
>>> https://repos.spark-packages.org and it will be the new home for the
>>> artifacts on spark-packages.
>>>
>>> Given the planned Bintray brown-out, this is a good time for us to test
>>> the new repository service. To consume artifacts from that, please replace "
>>> dl.bintray.com/spark-packages/maven" with "repos.spark-packages.org" in
>>> the Maven pom files or sbt build files in your repositories, e.g.:
>>> https://github.com/apache/spark/pull/32346
>>>
>>> We are still working on the release process to the new repository
>>> service, and will provide an update here shortly.
>>>
>>> If you have any questions for using the new repository service, or any
>>> general questions for spark-packages, please reach out to
>>> feedb...@spark-packages.org.
>>>
>>> Thanks,
>>> Bo
>>>
>>

Reply via email to