[RESULT][VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-11 Thread Christopher 
This vote passes with +3 (johndament, jmclean, elserj), and no -1.
Thanks all!

On Wed, Aug 10, 2016 at 4:27 PM Christopher  wrote:

> Just a quick reminder about this vote, which expires tomorrow. So far,
> there are +3
>
>
> On Tue, Aug 9, 2016 at 1:38 PM Josh Elser  wrote:
>
>> Forwarding my (binding) +1 from the PPMC vote.
>>
>> Christopher wrote:
>> > IPMC,
>> >
>> > 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:
>> >
>> >
>> https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E
>> >
>> > 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 fluo.io site has been redirected to fluo.apache.org (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
>> > fluo.apache.org 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:
>> >https://dist.apache.org/repos/dist/dev/incubator/fluo/
>> > and in a Nexus Staging repo:
>> >
>> https://repository.apache.org/content/repositories/orgapachefluo-1004
>> > for convenience.
>> >
>> > Signing key fingerprint is:
>> >8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>> > KEYS in:
>> >https://www.apache.org/dist/incubator/fluo/KEYS
>> >
>> > Git Commits (branches) in
>> > https://git-wip-us.apache.org/repos/asf/incubator-fluo.git:
>> >  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!
>> >
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-10 Thread Christopher 
Just a quick reminder about this vote, which expires tomorrow. So far,
there are +3

On Tue, Aug 9, 2016 at 1:38 PM Josh Elser  wrote:

> Forwarding my (binding) +1 from the PPMC vote.
>
> Christopher wrote:
> > IPMC,
> >
> > 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:
> >
> >
> https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E
> >
> > 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 fluo.io site has been redirected to fluo.apache.org (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
> > fluo.apache.org 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:
> >https://dist.apache.org/repos/dist/dev/incubator/fluo/
> > and in a Nexus Staging repo:
> >https://repository.apache.org/content/repositories/orgapachefluo-1004
> > for convenience.
> >
> > Signing key fingerprint is:
> >8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
> > KEYS in:
> >https://www.apache.org/dist/incubator/fluo/KEYS
> >
> > Git Commits (branches) in
> > https://git-wip-us.apache.org/repos/asf/incubator-fluo.git:
> >  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!
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-09 Thread Josh Elser 

Forwarding my (binding) +1 from the PPMC vote.

Christopher wrote:

IPMC,

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:

https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E

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 fluo.io site has been redirected to fluo.apache.org (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
fluo.apache.org 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:
   https://dist.apache.org/repos/dist/dev/incubator/fluo/
and in a Nexus Staging repo:
   https://repository.apache.org/content/repositories/orgapachefluo-1004
for convenience.

Signing key fingerprint is:
   8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
KEYS in:
   https://www.apache.org/dist/incubator/fluo/KEYS

Git Commits (branches) in
https://git-wip-us.apache.org/repos/asf/incubator-fluo.git:
 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!



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-08 Thread Christopher 
On Mon, Aug 8, 2016 at 8:47 PM Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - incubating in release name
> - DISCLAIMER exists
> - LICENSE and NOTICE fine
> - No binaries in the release
> - can compile from source
>
> Only one small niggle is that "build-resources-1.0.0-incubating” (one of
> the two artefacts in the release) seems an unusual name for an apache
> release as neither the project name or apache is mentioned in it’s name.
>
>
If it helps, I discussed the naming of these files in IRC with one of our
mentors, and copied the transcript to our dev@ list (
https://lists.apache.org/thread.html/e05a699ca15d629f2f82f6eec78ac0335116171ba32481720baad470@%3Cdev.fluo.apache.org%3E
)

The summary is that these are primarily intended for deployment to a Maven
repository (in particular, Maven Central via repository.apache.org), for
building Fluo projects, and they are marked with the "org.apache.fluo"
groupId. We felt that adding to the artifactId in Maven would introduce
redundancy and confusion.

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-08 Thread Justin Mclean 
Hi,

+1 binding

I checked:
- incubating in release name
- DISCLAIMER exists
- LICENSE and NOTICE fine
- No binaries in the release
- can compile from source

Only one small niggle is that "build-resources-1.0.0-incubating” (one of the 
two artefacts in the release) seems an unusual name for an apache release as 
neither the project name or apache is mentioned in it’s name.

The web site looks much better from a trademark/branding point of view. Thanks 
for be so responsive and quick addressing the issue(s) there.

Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-08 Thread Christopher 
On Mon, Aug 8, 2016 at 6:29 PM John D. Ament  wrote:

> +1 release contents look good.  Thank you for your due diligence on this
> release.
>
> I'll reply separately about the other comments, to not throw off this
> thread.
>
> 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
> owner.
>

That warning from gpg is not controllable by me. It's a warning about your
own local trust database. The warning indicates that you have not yet made
a determination of whether you trust my key or not. It usually follows the
message about the signature being valid (
https://www.gnupg.org/gph/en/manual/x334.html).

A fair number of folks have signed my key during previous ApacheCon
keysigning parties, so you may be able to trust my key transitively if you
trust one of theirs. Or, I think you can just set the trust level either
manually, or by signing it with your own key (maybe at the next ApacheCon
I'm able to attend).

Re: [VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-08 Thread John D. Ament 
+1 release contents look good.  Thank you for your due diligence on this
release.

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

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
owner.

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

> IPMC,
>
> 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:
>
>
> https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E
>
> 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 fluo.io site has been redirected to fluo.apache.org (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
> fluo.apache.org 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:
>   https://dist.apache.org/repos/dist/dev/incubator/fluo/
> and in a Nexus Staging repo:
>   https://repository.apache.org/content/repositories/orgapachefluo-1004
> for convenience.
>
> Signing key fingerprint is:
>   8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
> KEYS in:
>   https://www.apache.org/dist/incubator/fluo/KEYS
>
> Git Commits (branches) in
> https://git-wip-us.apache.org/repos/asf/incubator-fluo.git:
> 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!
>

[VOTE] Apache Fluo parent POM 1 and Build Resources 1.0.0

2016-08-08 Thread Christopher 
IPMC,

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:

https://lists.apache.org/thread.html/7f9a1db3798ddc4123ba3c66c632cedde6272ba55f1132d556f24a67@%3Cdev.fluo.apache.org%3E

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 fluo.io site has been redirected to fluo.apache.org (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
fluo.apache.org 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:
  https://dist.apache.org/repos/dist/dev/incubator/fluo/
and in a Nexus Staging repo:
  https://repository.apache.org/content/repositories/orgapachefluo-1004
for convenience.

Signing key fingerprint is:
  8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
KEYS in:
  https://www.apache.org/dist/incubator/fluo/KEYS

Git Commits (branches) in
https://git-wip-us.apache.org/repos/asf/incubator-fluo.git:
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!