Er, yeah uh oh. Did the staging repo accidentally get closed/released? Maybe I'm also missing something. If so then one way or the other we can't undo that as the 3.1.0 release in Maven, as far as I know. We can make a 3.1.1, but then it's kind of weird there was never any 3.1.0 source release.
We may well decide that, well, that 3.1.0 release was fine enough actually, that the blockers aren't actually that blocking. And the two mentioned so far don't sound so much like blockers. - If the Kafka problem happened in 3.0, then it isn't a regression from 3.0 to 3.1, technically - If CRAN wasn't working in 3.0.1, that's not a regression Naturally, of course, we may wish to fix those fast. And, we can create a 3.1.1 release fast if desired. But if that's the extent of it - no serious regressions - we might decide to just go ahead with this RC as the 3.1.0 release and move on to 3.1.1 quickly. At the least, again, would be weird to have no 3.1.0 actual release on the ASF if we can't undo this. FWIW the release looks OK to me as is, +1. I don't think the above are blockers. On Wed, Jan 6, 2021 at 1:38 PM Jacek Laskowski <ja...@japila.pl> wrote: > Hi, > > I'm curious why Spark 3.1.0 is already available in repo1.maven.org? > > https://repo1.maven.org/maven2/org/apache/spark/spark-core_2.12/3.1.0/ > > Pozdrawiam, > Jacek Laskowski > ---- > https://about.me/JacekLaskowski > "The Internals Of" Online Books <https://books.japila.pl/> > Follow me on https://twitter.com/jaceklaskowski > > <https://twitter.com/jaceklaskowski> > > > On Wed, Jan 6, 2021 at 1:01 AM Hyukjin Kwon <gurwls...@gmail.com> wrote: > >> Please vote on releasing the following candidate as Apache Spark version >> 3.1.0. >> >> The vote is open until January 8th 4PM 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 3.1.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.1.0-rc1 (commit >> 97340c1e34cfd84de445b6b7545cfa466a1baaf6): >> https://github.com/apache/spark/tree/v3.1.0-rc1 >> >> The release files, including signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-rc1-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-1363/ >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-rc1-docs/ >> >> The list of bug fixes going into 3.1.0 can be found at the following URL: >> https://s.apache.org/ldzzl >> >> This release is using the release script of the tag v3.1.0-rc1. >> >> 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 via "pip install >> https://dist.apache.org/repos/dist/dev/spark/v3.1.0-rc1-bin/pyspark-3.1.0.tar.gz >> " >> 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 3.1.0? >> =========================================== >> >> The current list of open tickets targeted at 3.1.0 can be found at: >> https://issues.apache.org/jira/projects/SPARK and search for "Target >> Version/s" = 3.1.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. >> >>
