I was trying to avoid changing the version names and revert the changes on master again. But you are right it might lead to confusions which release script is used for RC2, I'll follow your advice and create a new RC2 tag.
Thanks! Xingbo On Wed, Oct 30, 2019 at 5:06 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > Hi, Xingbo. > > Currently, RC2 tag is pointing RC1 tag. > > https://github.com/apache/spark/tree/v3.0.0-preview-rc2 > > Could you cut from the HEAD of master branch? > Otherwise, nobody knows what release script you used for RC2. > > Bests, > Dongjoon. > > > > On Wed, Oct 30, 2019 at 4:15 PM Xingbo Jiang <jiangxb1...@gmail.com> > wrote: > >> Hi all, >> >> This RC fails because: >> It fails to generate a PySpark release. >> >> I'll start RC2 soon. >> >> Thanks! >> >> Xingbo >> >> >> On Wed, Oct 30, 2019 at 4:10 PM Xingbo Jiang <jiangxb1...@gmail.com> >> wrote: >> >>> Thanks Sean, since we need to generate PySpark release with a different >>> name, I would prefer fail RC1 and start another release candidate. >>> >>> Sean Owen <sro...@gmail.com> 于2019年10月30日周三 下午4:00写道： >>> >>>> I agree that we need a Pyspark release for this preview release. If >>>> it's a matter of producing it from the same tag, we can evaluate it >>>> within this same release candidate. Otherwise, just roll another >>>> release candidate. >>>> >>>> I was able to build it and pass all tests with JDK 8 and JDK 11 >>>> (hadoop-3.2 profile, note) on Ubuntu, so this is otherwise looking >>>> good to me. >>>> >>>> On Tue, Oct 29, 2019 at 9:01 PM Xingbo Jiang <jiangxb1...@gmail.com> >>>> wrote: >>>> > >>>> > Please vote on releasing the following candidate as Apache Spark >>>> version 3.0.0-preview. >>>> > >>>> > The vote is open until November 2 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.0.0-preview >>>> > [ ] -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-preview-rc1 (commit >>>> 5eddbb5f1d9789696927f435c55df887e50a1389): >>>> > https://github.com/apache/spark/tree/v3.0.0-preview-rc1 >>>> > >>>> > The release files, including signatures, digests, etc. can be found >>>> at: >>>> > https://dist.apache.org/repos/dist/dev/spark/v3.0.0-preview-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-1334/ >>>> > >>>> > The documentation corresponding to this release can be found at: >>>> > https://dist.apache.org/repos/dist/dev/spark/v3.0.0-preview-rc1-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 >>>> > >>>> > 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. >>>> >>>
