fluo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject [VOTE] Fluo 1.2.0-rc1
Date Wed, 21 Feb 2018 21:45:59 GMT
Fluo Developers,

I finally had a chance to prep a release candidate for 1.2.0-rc1! Yay!
Please consider the following candidate for Fluo 1.2.0.

Git Commit:
    678adebfbd97483bbef7707b6ac5eb357540dea3
Branch:
    1.2.0-rc1

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 \
    678adebfbd97483bbef7707b6ac5eb357540dea3

Staging repo:
https://repository.apache.org/content/repositories/orgapachefluo-1023
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapachefluo-1023/org/apache/fluo/fluo/1.2.0/fluo-1.2.0-source-release.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapachefluo-1023/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 Feb 24 22:00:00 UTC 2018 (Sat
Feb 24 17:00:00 EST 2018 / Sat Feb 24 14:00: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-1023/
    # note the trailing slash is needed

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message