incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <>
Subject Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0
Date Mon, 08 Aug 2016 22:29:07 GMT
+1 release contents look good.  Thank you for your due diligence on this

I'll reply separately about the other comments, to not throw off this

Nitpick: Check your signature, may not be valid:

gpg: WARNING: This key is not certified with a trusted signature!

gpg:          There is no indication that the signature belongs to the

On Mon, Aug 8, 2016 at 5:24 PM Christopher <> wrote:

> Please consider the following candidates for Fluo Parent POM 1-incubating
> and Fluo Build Resources 1.0.0-incubating. There are two artifacts, which
> we are releasing together. They do not contain Fluo itself, but are
> prerequisites for the Maven build of Fluo, which will be released via Maven
> upon successful passing of this vote. Releasing these to Maven will bring
> us a step closer to preparing release candidates for Fluo itself.
> Passing PPMC release vote thread:
> Since the last attempted vote, we have taken significant steps to ensure
> that Apache retains exclusive use of the Fluo trademark. Historical
> releases still exist in Maven Central under the "io.fluo" groupId, but the
> original site has been redirected to (until its
> domain registration expires, at which point our plan is to let it lapse),
> and references to pre-Apache releases have been marked explicitly as such
> on the Fluo website. The organization containing related 3rd party software
> for Fluo was renamed in GitHub from fluo-io to astralway, so as not to
> misappropriate the Fluo trademark, and references to Fluo on those external
> projects have made it a point to explicitly refer to "Apache Fluo". The
> website will continue to be updated as we start making
> Apache releases, but we don't anticipate any future trademark concerns such
> as those noted in the previously canceled vote thread. Please let us know
> if we've overlooked something.
> Release artifacts are staged at:
> and in a Nexus Staging repo:
> for convenience.
> Signing key fingerprint is:
>   8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
> KEYS in:
> Git Commits (branches) in
>     02d4ea2332598a94285985ee8a1c8e92a42b4770 (build-resources-1.0.0-rc1)
>     95c48e3f14faf5cdca259d8ec60ec68b640fce1e (fluo-parent-1-rc3)
> If this vote passes, gpg-signed tags will be created using:
>     git tag -f -m 'Apache Fluo Build Resources 1.0.0-incubating' -s
> rel/build-resources-1.0.0-incubating
> 02d4ea2332598a94285985ee8a1c8e92a42b4770
>     git tag -f -m 'Apache Fluo Parent POM 1-incubating' -s
> rel/fluo-parent-1-incubating 95c48e3f14faf5cdca259d8ec60ec68b640fce1e
> 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-incubating release of Apache Fluo Parent POM
> and 1.0.0-incubating release of Apache Fluo Build Resources.
> This vote will end on Thu Aug 11 21:30:00 UTC 2016
> (Thu Aug 11 17:30:00 EDT 2016 / Thu Aug 11 14:30:00 PDT 2016)
> Thanks!

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