This is a test release candidate for Fluo 1.2.0, in case anybody wants to
do any more tests with it. If things worked out okay, I'll create another
one to actually vote on within the next few days.

The rest of this message is generated, so disregard any reference to voting
below:

=============

Fluo Developers,

Please consider the following candidate for Fluo 1.2.0.

Git Commit:
    de13436abec28ac5a8a57bd034b7091504030239
Branch:
    1.2.0-rc0

If this vote passes, a gpg-signed tag will be created using:
    git tag -f -m 'Apache Fluo 1.2.0' -s rel/fluo-1.2.0 \
    de13436abec28ac5a8a57bd034b7091504030239

Staging repo:
https://repository.apache.org/content/repositories/orgapachefluo-1022
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapachefluo-1022/org/apache/fluo/fluo/1.2.0/fluo-1.2.0-source-release.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapachefluo-1022/org/apache/fluo/fluo/1.2.0/fluo-1.2.0-bin.tar.gz
(Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
given artifact.)

All artifacts were built and staged with:
    mvn release:prepare && mvn release:perform

Signing keys are available at https://www.apache.org/dist/fluo/KEYS
(Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)

Release notes (in progress) can be found at:
https://fluo.apache.org/release/fluo-1.2.0/

Please vote one of:
[ ] +1 - I have verified and accept...
[ ] +0 - I have reservations, but not strong enough to vote against...
[ ] -1 - Because..., I do not accept...
... these artifacts as the 1.2.0 release of Apache Fluo.

This vote will remain open until at least Sat Jan 13 22:30:00 UTC 2018 (Sat
Jan 13 17:30:00 EST 2018 / Sat Jan 13 14:30:00 PST 2018).
Voting can continue after this deadline until the release manager sends an
email ending the vote.

Thanks!

P.S. Hint: download the whole staging repo with
    wget -erobots=off -r -l inf -np -nH \
    https://repository.apache.org/content/repositories/orgapachefluo-1022/
    # note the trailing slash is needed

Reply via email to