Hi all,

As I wrote yesterday, I'd like to call a vote to release Apache DataFu
2.0.0. Like our last release, this is only datafu-spark (there are no
changes in the other modules). The major change of this release is of
course Spark 3 support. As we discussed in the last two pull requests,
this release will - officially - support Spark 3.0.0-3.1.3. Newer
versions break compilation because of our UDAFs, so this release
introduced replacement APIs and deprecated the old UDAFs. In our next
release - coming soon! - we will remove the problematic code and then
we should be able to support newer Spark versions.

For a summary of the changes in this release, see:
https://github.com/apache/datafu/blob/release-2.0.0-rc0/changes.md

The source release candidate RC0 can be downloaded here:
https://dist.apache.org/repos/dist/dev/datafu/apache-datafu-2.0.0-rc0/

The artifact (i.e. JAR) for this release candidate can be
found here:

https://repository.apache.org/content/repositories/orgapachedatafu-1017

Instructions for how to build against the artifacts in the staging
repository can be found in the RELEASE instructions
(https://github.com/apache/datafu/blob/main/RELEASE.md).

Files have been signed with PGP key
07C730990051711FF5F5C2BDDD1501E422A109F1, corresponding to
e...@apache.org, which can be found on
https://people.apache.org/keys/committer/eyal.asc. This key can also
be found on keyservers (e.g. gpg --keyserver keys.openpgp.org
--search-key 07C730990051711FF5F5C2BDDD1501E422A109F1).

Instructions for how to verify checksums and signatures can be found
in the README (https://github.com/apache/datafu/blob/main/README.md).

The release candidate has been tagged with release-2.0.0-rc0, which
has been signed with the same key.  I've also created a branch 2.0.0.

Please download the release candidate, check the hashes, check the
signatures, test it, and vote.  The vote will be open for 72 hours
(ends on January 13th at 8 a.m. GMT+3).

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

My vote: +1

Thanks,
Eyal Allweil

Reply via email to