Therefore, if I want to build my product against these jars I need to either 
locally install these jars or checkout and build the RC tag.

I guess I need to build anyway because I need a 
spark-hadoop-cloud_2.12-3.0.0.jar. BTW, it would be incredibly handy to have 
this in the distro, or at least in Maven Central.

Thanks,

Steve C

On 1 Apr 2020, at 3:48 pm, Wenchen Fan 
<cloud0...@gmail.com<mailto:cloud0...@gmail.com>> wrote:

Yea, release candidates are different from the preview version, as release 
candidates are not official releases, so they won't appear in Maven Central, 
can't be downloaded in the Spark official website, etc.

On Wed, Apr 1, 2020 at 12:32 PM Sean Owen 
<sro...@gmail.com<mailto:sro...@gmail.com>> wrote:
These are release candidates, not the final release, so they won't be published 
to Maven Central. The naming matches what the final release would be.

On Tue, Mar 31, 2020 at 11:25 PM Stephen Coy 
<s...@infomedia.com.au.invalid<mailto:s...@infomedia.com.au.invalid>> wrote:
Furthermore, the spark jars in these bundles all look like release versions:

[scoy@Steves-Core-i9 spark-3.0.0-bin-hadoop3.2]$ ls -l jars/spark-*
-rw-r--r--@ 1 scoy  staff  9261223 31 Mar 20:55 
jars/spark-catalyst_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  9720421 31 Mar 20:55 jars/spark-core_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   430854 31 Mar 20:55 jars/spark-graphx_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  2076394 31 Mar 20:55 
jars/spark-hive-thriftserver_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   690789 31 Mar 20:55 jars/spark-hive_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   369189 31 Mar 20:55 
jars/spark-kubernetes_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    59870 31 Mar 20:55 
jars/spark-kvstore_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    75930 31 Mar 20:55 
jars/spark-launcher_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   294692 31 Mar 20:55 jars/spark-mesos_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   111915 31 Mar 20:55 
jars/spark-mllib-local_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  5884976 31 Mar 20:55 jars/spark-mllib_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  2397168 31 Mar 20:55 
jars/spark-network-common_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    87065 31 Mar 20:55 
jars/spark-network-shuffle_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    52605 31 Mar 20:55 jars/spark-repl_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    30347 31 Mar 20:55 jars/spark-sketch_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  7092213 31 Mar 20:55 jars/spark-sql_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff  1137675 31 Mar 20:55 
jars/spark-streaming_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff     9049 31 Mar 20:55 
jars/spark-tags_2.12-3.0.0-tests.jar
-rw-r--r--@ 1 scoy  staff    15149 31 Mar 20:55 jars/spark-tags_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff    51089 31 Mar 20:55 jars/spark-unsafe_2.12-3.0.0.jar
-rw-r--r--@ 1 scoy  staff   329764 31 Mar 20:55 jars/spark-yarn_2.12-3.0.0.jar

At least they have not yet shown up on Maven Central…

Steve C

On 1 Apr 2020, at 3:18 pm, Stephen Coy 
<s...@infomedia.com.au.INVALID<mailto:s...@infomedia.com.au.INVALID>> wrote:

The download artifacts are all seem to have the “RC1” missing from their names.

e.g. spark-3.0.0-bin-hadoop3.2.tgz

Cheers,

Steve C

On 1 Apr 2020, at 2:04 pm, Reynold Xin 
<r...@databricks.com<mailto:r...@databricks.com>> wrote:


Please vote on releasing the following candidate as Apache Spark version 3.0.0.

The vote is open until 11:59pm Pacific time Fri Apr 3, 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/<https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspark.apache.org%2F&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147450885&sdata=uNMU5zofa%2FIJb4PYu0wBaG2%2FOMxeP1kKkDTsPCz4HWg%3D&reserved=0>

The tag to be voted on is v3.0.0-rc1 (commit 
6550d0d5283efdbbd838f3aeaf0476c7f52a0fb1):
https://github.com/apache/spark/tree/v3.0.0-rc1<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fspark%2Ftree%2Fv3.0.0-rc1&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147460879&sdata=gYnktFn6exFW83IhnIBD%2FMbDrvh%2FM1VWv%2FtKcSM2YfY%3D&reserved=0>

The release files, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc1-bin/<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fspark%2Fv3.0.0-rc1-bin%2F&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147460879&sdata=E%2BK0RAomOP2ytZfGYCJN3%2BhICjPHKHMJPQDbaqAY%2FKA%3D&reserved=0>

Signatures used for Spark RCs can be found in this file:
https://dist.apache.org/repos/dist/dev/spark/KEYS<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fspark%2FKEYS&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147470878&sdata=F7e8%2FfnnO95wl%2Bvok1sYHMYT%2BMMN1UWASwJdAcEU71s%3D&reserved=0>

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapachespark-1341/<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachespark-1341%2F&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147480872&sdata=cQknf8SIPVQdT0wuEo%2FzAxtqWv1km4H80o%2FPQOyjXtk%3D&reserved=0>

The documentation corresponding to this release can be found at:
https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc1-docs/<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fspark%2Fv3.0.0-rc1-docs%2F&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147480872&sdata=UH8EXq7xpAfoS5VBCAOFs%2BKvItldRMck9glCvJe%2B%2Bvk%3D&reserved=0>

The list of bug fixes going into 2.4.5 can be found at the following URL:
https://issues.apache.org/jira/projects/SPARK/versions/12339177<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fprojects%2FSPARK%2Fversions%2F12339177&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147490870&sdata=yPRUZsz366KW%2BA8Oej4kIAa1LDjWlDOvEPPugWdmdtU%3D&reserved=0>

This release is using the release script of the tag v3.0.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 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fprojects%2FSPARK&data=02%7C01%7Cscoy%40infomedia.com.au%7Cef53a46c6f004248f97f08d7d5f7ee18%7C45d5407150f849caa59f9457123dc71c%7C0%7C0%7C637213133147500869&sdata=iHaNUPUU0wzuyPJOUzC50YNa6umJ2rWaEx1XilIn8Fw%3D&reserved=0>
 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.


Note: I fully expect this RC to fail.




This email contains confidential information of and is the copyright of 
Infomedia. It must not be forwarded, amended or disclosed without consent of 
the sender. If you received this message by mistake, please advise the sender 
and delete all copies. Security of transmission on the internet cannot be 
guaranteed, could be infected, intercepted, or corrupted and you should ensure 
you have suitable antivirus protection in place. By sending us your or any 
third party personal details, you consent to (or confirm you have obtained 
consent from such third parties) to Infomedia’s privacy policy. 
http://www.infomedia.com.au/privacy-policy/


Reply via email to