Mentors needed for Superset and Samoa

[Alan Gates]

It is time for me to step down from the Incubator PMC.  Before I officially
depart I'd like to help the podlings I am currently mentoring, Superset and
Samoa, find new mentors.  If anyone has time and interest in mentoring
these projects I would greatly appreciate their stepping in to replace me.

"Superset is an enterprise-ready web application for data exploration, data
visualization and dashboarding."  The project has been growing the
community and making regular releases and is nearing graduation.

>From Samoa's self description: "SAMOA provides a collection of distributed
streaming algorithms for the most common data mining and machine learning
tasks such as classification, clustering, and regression, as well as
programming abstractions to develop new algorithms that run on top of
distributed stream processing engines (DSPEs). It features a pluggable
architecture that allows it to run on several DSPEs such as Apache Storm,
Apache S4, and Apache Samza."  The project has been in incubation for 5
years now and has at times struggled to keep momentum, though it has
recently added a new committer and made a release.

Alan.

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Alan Gates]

+1.  I checked the disclaimer, license, and notice files, the hash and key
signature.  I did a build from source and ran the rat check.

One note on the rat check, five files fail.  One of those is s shell script
that could have the license added, the others look like maybe they
couldn't.  But it would be nice to put those in the exclude list so the rat
build succeeds.  This can be done after this release.

Alan.

On Tue, Mar 24, 2020 at 3:14 PM Justin Mclean 
wrote:

> Hi,
>
> > So the best I could do was to include the SHA512 with the developer
> artefacts.
>
> That all that’s needed change my vote to:
>
> +1 (binding)
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Alan Gates]

I’ll take a look this weekend or early next week. 

Alan. 

Sent from my iPhone

> On Apr 10, 2020, at 17:53, Justin Mclean  wrote:
> 
> Hi,
> 
> Look like this needs another IPMC vote, can any IPMC member help?
> 
> Thanks,
> Justin
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

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

Re: [VOTE] Release Apache Superset (incubating) version 0.35.2

[Alan Gates]

+1.  I checked the LICENSE, NOTICE, and DISCLAIMER files, and the
signatures.  Looked for any files that weren't properly licensed and
checked for any non-image binaries.

One small note for next time, you should update the copyright notice in the
NOTICE file to 2020.

Alan.

On Mon, Jan 13, 2020 at 7:10 AM Ville Brofeldt 
wrote:

> Justin and Paul,
>
> Thank you for the feedback and vote; the pointers regarding the
> documentation were very helpful, and we will make sure to address them in
> time for the next release.
>
> Thanks,
> The Apache Superset (Incubating) Team
>
> On Sun, Jan 12, 2020 at 11:20 PM Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> wrote:
>
> > Dear IPMC,
> >
> > as the 72 hour voting window has now closed with zero votes, this is a
> > kind reminder to vote on the release candidate for Apache Superset
> > (Incubating) 0.35.2, which includes several important improvements to the
> > current stable release (0.35.1).
> >
> > Respectfully,
> >
> > The Apache Superset (Incubating) Team
> >
> > On Thu, Jan 9, 2020 at 9:14 PM Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > wrote:
> >
> >> Hello IPMC,
> >>
> >>
> >> The Apache Superset (incubating) community has voted on and approved a
> >> proposal to
> >>
> >> release Apache Superset (incubating) version 0.35.2.
> >>
> >> The voting thread can be found here:
> >>
> https://lists.apache.org/thread.html/rf8b1cbe6c880d408583448e5a96e08b90da1258c7cdaf4658836%40%3Cdev.superset.apache.org%3E
> >>
> >>
> >> We now kindly request the Incubator PMC members review and vote on this
> >>
> >> incubator release.
> >>
> >>
> >> Apache Superset (incubating) is a modern, enterprise-ready business
> >> intelligence web application.
> >>
> >>
> >> The release candidate:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.2rc2/
> >>
> >>
> >> Git tag for the release:
> >>
> >> https://github.com/apache/incubator-superset/tree/0.35.2rc2
> >>
> >>
> >> The Change Log for the release:
> >>
> >>
> https://github.com/apache/incubator-superset/blob/0.35.2rc2/CHANGELOG.md
> >>
> >>
> >> public keys are available at:
> >>
> >>
> >> https://www.apache.org/dist/incubator/superset/KEYS
> >>
> >>
> >> The vote will be open for at least 72 hours or until the necessary
> number
> >>
> >> of votes are reached.
> >>
> >>
> >> Please vote accordingly:
> >>
> >>
> >> [ ] +1 approve
> >>
> >> [ ] +0 no opinion
> >>
> >> [ ] -1 disapprove with the reason
> >>
> >>
> >> Thanks,
> >>
> >> The Apache Superset (Incubating) Team
> >>
> >
>

Re: Omid -> Phoenix sub-project next steps

[Alan Gates]

I think you should go ahead.  Everyone's voted on it, no one made any
comments on the discussion thread on general@, and Justin's been aware of
what's going on the whole way.

Alan.

On Thu, Nov 14, 2019 at 8:32 AM Josh Elser  wrote:

> I'm a bit confused about where we go from this point.
>
> Given the doc[1] that Alan shared last time, we are good to move ahead
> with the logistical changes.
>
> Further, the next guide[2] simply says that VP Phoenix (me) should
> coordinate with VP Incubator.
>
> Should I go ahead and file the TLP Parent Request with Infra?
>
> - Josh
>
> [1]
>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject
> [2] https://incubator.apache.org/guides/transferring.html
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omid and Tephra graduating into Phoenix

[Alan Gates]

I've reverted the change for now to avoid breaking any builds.  Once we've
either sorted out how to mark these as graduating or Phoenix has finished
it's work and we have a link to resolve to, then I'll redo this.

Alan.

On Fri, Nov 8, 2019 at 2:26 PM Alan Gates  wrote:

> Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at
> this point.
>
> Alan.
>
> On Fri, Nov 8, 2019 at 2:21 PM Alan Gates  wrote:
>
>> I found the instructions for that here:
>> https://incubator.apache.org/guides/transferring.html
>> I didn't put in the resolution link yet because there's no such link
>> yet.
>>
>> Alan.
>>
>> On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher  wrote:
>>
>>> Hi Alan,
>>>
>>> The podlings.xml change is not really correct. It’s not documented but
>>> instead of  you need to have a something like this for each:
>>>
>>> https://phoenix.apache.org/omid/“/>
>>>
>>> This creates the a link on the table on
>>> https://incubator.apache.org/projects
>>>
>>> Also, there is no “graduating” status.
>>>
>>> >> sponsor="Incubator" startdate="2016-03-28”>
>>>
>>> must be
>>>
>>>     >> sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>>>
>>> Whimsy may very well break unless this is fixed. The daily Incubator
>>> site update may break as well.
>>>
>>> Regards,
>>> Dave
>>>
>>> > On Nov 8, 2019, at 1:25 PM, Alan Gates  wrote:
>>> >
>>> > I've updated the status of Omid and Tephra to 'graduating' in
>>> > podlings.xml.  I've also updated the projects/${podling}.xml for each
>>> of
>>> > them with info on the SGAs (which hadn't been put there) and on their
>>> > status as graduating into Phoenix.
>>> >
>>> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
>>> Once
>>> > this is done I can update the status to 'graduated' in podlings.xml.
>>> >
>>> > Alan.
>>> >
>>> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean >> >
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >>> I don't think so.  I'll wait the 72 hours for the comment period to
>>> end
>>> >>> (started this morning) and then add a note to the report that Omid
>>> and
>>> >>> Tephra are graduating into Phoenix, unless Justin prefers something
>>> else.
>>> >>
>>> >>
>>> >> That's fine I’ve already note this in the report.
>>> >>
>>> >> Thanks,
>>> >> Justin
>>> >> -
>>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>>> >>
>>> >>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>

Re: Omid and Tephra graduating into Phoenix

[Alan Gates]

Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at this
point.

Alan.

On Fri, Nov 8, 2019 at 2:21 PM Alan Gates  wrote:

> I found the instructions for that here:
> https://incubator.apache.org/guides/transferring.html
> I didn't put in the resolution link yet because there's no such link yet.
>
> Alan.
>
> On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher  wrote:
>
>> Hi Alan,
>>
>> The podlings.xml change is not really correct. It’s not documented but
>> instead of  you need to have a something like this for each:
>>
>> https://phoenix.apache.org/omid/“/>
>>
>> This creates the a link on the table on
>> https://incubator.apache.org/projects
>>
>> Also, there is no “graduating” status.
>>
>> > sponsor="Incubator" startdate="2016-03-28”>
>>
>> must be
>>
>> > sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>>
>> Whimsy may very well break unless this is fixed. The daily Incubator site
>> update may break as well.
>>
>> Regards,
>> Dave
>>
>> > On Nov 8, 2019, at 1:25 PM, Alan Gates  wrote:
>> >
>> > I've updated the status of Omid and Tephra to 'graduating' in
>> > podlings.xml.  I've also updated the projects/${podling}.xml for each of
>> > them with info on the SGAs (which hadn't been put there) and on their
>> > status as graduating into Phoenix.
>> >
>> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
>> Once
>> > this is done I can update the status to 'graduated' in podlings.xml.
>> >
>> > Alan.
>> >
>> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean 
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >>> I don't think so.  I'll wait the 72 hours for the comment period to
>> end
>> >>> (started this morning) and then add a note to the report that Omid and
>> >>> Tephra are graduating into Phoenix, unless Justin prefers something
>> else.
>> >>
>> >>
>> >> That's fine I’ve already note this in the report.
>> >>
>> >> Thanks,
>> >> Justin
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: Omid and Tephra graduating into Phoenix

[Alan Gates]

I found the instructions for that here:
https://incubator.apache.org/guides/transferring.html
I didn't put in the resolution link yet because there's no such link yet.

Alan.

On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher  wrote:

> Hi Alan,
>
> The podlings.xml change is not really correct. It’s not documented but
> instead of  you need to have a something like this for each:
>
> https://phoenix.apache.org/omid/“/>
>
> This creates the a link on the table on
> https://incubator.apache.org/projects
>
> Also, there is no “graduating” status.
>
>  sponsor="Incubator" startdate="2016-03-28”>
>
> must be
>
>  sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>
> Whimsy may very well break unless this is fixed. The daily Incubator site
> update may break as well.
>
> Regards,
> Dave
>
> > On Nov 8, 2019, at 1:25 PM, Alan Gates  wrote:
> >
> > I've updated the status of Omid and Tephra to 'graduating' in
> > podlings.xml.  I've also updated the projects/${podling}.xml for each of
> > them with info on the SGAs (which hadn't been put there) and on their
> > status as graduating into Phoenix.
> >
> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
> Once
> > this is done I can update the status to 'graduated' in podlings.xml.
> >
> > Alan.
> >
> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean 
> > wrote:
> >
> >> Hi,
> >>
> >>> I don't think so.  I'll wait the 72 hours for the comment period to end
> >>> (started this morning) and then add a note to the report that Omid and
> >>> Tephra are graduating into Phoenix, unless Justin prefers something
> else.
> >>
> >>
> >> That's fine I’ve already note this in the report.
> >>
> >> Thanks,
> >> Justin
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omid and Tephra graduating into Phoenix

[Alan Gates]

I've updated the status of Omid and Tephra to 'graduating' in
podlings.xml.  I've also updated the projects/${podling}.xml for each of
them with info on the SGAs (which hadn't been put there) and on their
status as graduating into Phoenix.

I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.  Once
this is done I can update the status to 'graduated' in podlings.xml.

Alan.

On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean 
wrote:

> Hi,
>
> > I don't think so.  I'll wait the 72 hours for the comment period to end
> > (started this morning) and then add a note to the report that Omid and
> > Tephra are graduating into Phoenix, unless Justin prefers something else.
>
>
> That's fine I’ve already note this in the report.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omid and Tephra graduating into Phoenix

[Alan Gates]

I don't think so.  I'll wait the 72 hours for the comment period to end
(started this morning) and then add a note to the report that Omid and
Tephra are graduating into Phoenix, unless Justin prefers something else.

Alan.

On Tue, Nov 5, 2019 at 5:14 PM Andreas Neumann  wrote:

> Should Tephra still file a podling report this month?
> -Andreas
>
> On Tue, Nov 5, 2019 at 12:00 PM Dave Fisher  wrote:
>
> > For the changes to podlings.xml one example of a graduation to a
> > subproject is DistributedLog.
> >
> > Regards,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On Nov 5, 2019, at 11:50 AM, Alan Gates  wrote:
> > >
> > > Omid[1] and Tephra[2] have voted to join the Phoenix community as
> > > sub-projects.  Phoenix has voted to accept them[3].  Per the
> instructions
> > > at [4], this email is notice of that.  Unless any objections are raised
> > in
> > > 72 hours the graduation will be considered accepted and both podlings
> > will
> > > move ahead with the details.
> > >
> > > Alan.
> > >
> > > 1.
> > >
> >
> https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E
> > > 2.
> > >
> >
> https://lists.apache.org/thread.html/33487013c347fe15f43a55cc2281613e1cce4f0cd07d27280ddad9bb@%3Cdev.tephra.apache.org%3E
> > > 3.
> > >
> >
> https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E
> > > 4.
> > >
> >
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Omid and Tephra graduating into Phoenix

[Alan Gates]

Omid[1] and Tephra[2] have voted to join the Phoenix community as
sub-projects.  Phoenix has voted to accept them[3].  Per the instructions
at [4], this email is notice of that.  Unless any objections are raised in
72 hours the graduation will be considered accepted and both podlings will
move ahead with the details.

Alan.

1.
https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E
2.
https://lists.apache.org/thread.html/33487013c347fe15f43a55cc2281613e1cce4f0cd07d27280ddad9bb@%3Cdev.tephra.apache.org%3E
3.
https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E
4.
https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject

Re: [VOTE] Release Apache Superset (incubating) 0.35.0 [RC3]

[Alan Gates]

Forwarding my +1 from the dev list.  I checked the LICENSE, NOTICE, and
DISCLAIMER files, the signature and hash, and checked for any improperly
licensed or binary files (there are some font and image files, but these
are ok).

Alan.

On Mon, Nov 4, 2019 at 1:33 AM daniel gaspar 
wrote:

> Hi IPMC,
>
> The Apache Superset PPMC and IPMC recently passed a voting for RC2,
> but I just realized there is a minor issue. The issue
> was that the version was labelled `0.35.0rc2` inside the tarball, as
> opposed to `0.35.0`, meaning that when installing from source, the Python &
> npm packages would appear to be a `0.35.0rc2`.
>
> 0.35.0rc3 solves this issue, as the version is labelled `0.35.0` inside the
> tarball.
> Also included the latest CHANGELOG.
>
> These are the 2 commits on top of RC2:
> 49d672eb Update changelog
> d2cfebe6 Fix, package version bump to 0.35.0
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a business intelligence web application
>
> The community voting thread (for RC2) can be found here:
>
> https://lists.apache.org/thread.html/1f30339c9e559eafea642ed0ab10eb766b55a29c62ed1fc7fd6ca182@%3Cdev.superset.apache.org%3E
>
> The release candidate has been tagged in GitHub as tag 0.35.0rc3
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.35.0rc3
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.0rc3/
>
> Release artifacts are signed with the key located here:
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Superset (incubating)
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> community to validate this release.
>
> On behalf of the Apache Superset Community,
> Daniel Gaspar
>

Re: Omid and Tephra

[Alan Gates]

Regarding SGAs, here's the JIRA for Omid:
https://issues.apache.org/jira/browse/OMID-2
According to
https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask
(original creators of Tephra) submitted a SGA for it and it's one file, but
I don't know where the referenced file is kept.

Alan.

On Wed, Oct 30, 2019 at 10:32 AM Alan Gates  wrote:

> Bertand, thanks for bringing this up.  I'll chase those down.
>
> Alan.
>
> On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
>> Hi,
>>
>> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
>> > ...My current expectation is that we'd just rename the existing Git
>> > repositories and change the LDAP group which are used to determine write
>> > access...
>>
>> From the Incubator's point of view, I think an additional step is to
>> confirm and document if any Software Grants were needed for these
>> projects code and if yes if they've been filed as needed.
>>
>> This can be just a jira or other ticket documenting the move and
>> including this info.
>>
>> -Bertrand
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: Omid and Tephra

[Alan Gates]

Bertand, thanks for bringing this up.  I'll chase those down.

Alan.

On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
> > ...My current expectation is that we'd just rename the existing Git
> > repositories and change the LDAP group which are used to determine write
> > access...
>
> From the Incubator's point of view, I think an additional step is to
> confirm and document if any Software Grants were needed for these
> projects code and if yes if they've been filed as needed.
>
> This can be just a jira or other ticket documenting the move and
> including this info.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omid and Tephra

[Alan Gates]

Makes sense.  I've replied to the discussion in the Phoenix community so we
know what terms Tephra and Omid are voting on.  As soon as I hear from them
I'll start votes in both communities.

Alan.

On Tue, Oct 29, 2019 at 3:47 PM Andreas Neumann  wrote:

> I agree with Justin, I think we get - at least in the Tephra community - a
> quorum.
> -Andreas
>
> On Mon, Oct 28, 2019 at 12:09 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > According to [4] the first step of graduating into a sub-project of an
> > > existing TLP is a vote by the podling.  Given that both podlings have
> > very
> > > low activity I am not sure we will get the necessary votes to make this
> > > happen.
> >
> > I would try and see what happens - the mentors have binding votes so
> > hopefully they will vote. If we don’t get enough votes or if someone
> raises
> > an objection we’ll decide what to do then.
> >
> > > One question that I'd like to see resolved as part of this vote
> > > is what status Phoenix plans to grant to Tephra and Omid committers and
> > > PPMC members.
> >
> > I would ask all PPMC and committers if they want to be part of Phoenix
> > PMC/committers and grant those who reply. But if the Phoenix PMC has
> other
> > ideas they could also be considered.
> >
> > If someone at a later point decides to “opt-in” you may want to consider
> > that as well.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Omid and Tephra

[Alan Gates]

There appears to be consensus on this thread, as well as in the Phoenix
community[1] that it makes sense for Phoenix to adopt both Omid and
Tephra.  My mails to the Tephra and Omid communities[2][3] have gone
unanswered, so I assume silence implies consent.

According to [4] the first step of graduating into a sub-project of an
existing TLP is a vote by the podling.  Given that both podlings have very
low activity I am not sure we will get the necessary votes to make this
happen.  I can start the vote threads in each podling, but I believe we
should be ready to move forward without these votes passing due to lack of
participation.

The next step is for the Phoenix PMC to formally vote to accept the
podlings.  One question that I'd like to see resolved as part of this vote
is what status Phoenix plans to grant to Tephra and Omid committers and
PPMC members.  Normally I would expect that all podling committers become
TLP committers, but given the low participation it may make sense for
Phoenix to use an opt-in where podling committers need to affirm their
desire to continue on the project before being made committers.

Alan.

1.
https://lists.apache.org/thread.html/ec00615cbbb4225885e3776f1e8fd071600a9c50f35769f453b8a779@%3Cdev.phoenix.apache.org%3E
2.
https://lists.apache.org/thread.html/21deb9e6fe0e929af38b9b712cc0a0779b170f6617b6dee21cfbc356@%3Cdev.tephra.apache.org%3E
3.
https://lists.apache.org/thread.html/3fda8fe4517e7d78e4a38b75cce0d77e4514529d50249c190fcb3bda@%3Cdev.omid.apache.org%3E
4.
https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject


On Fri, Oct 25, 2019 at 10:35 AM Ohad Shacham
 wrote:

> +1, Thanks Alan.
> Just wanted to verify that adopt means Omid and Tephra will sit in the same
> repo as Phoenix but will be able to checkout separately as well. I assume
> this is Phoenix folks decision.
> I know that in Yahoo Omid is used internally.
>
> On Fri, Oct 25, 2019 at 2:36 AM Gary Helmling  wrote:
>
> > +1 this seems like the best option.
> >
> > On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell 
> > wrote:
> >
> > > +1 this would be a good outcome. Both Tephra and OMID are good
> > > technologies, with respective pros and cons, and Phoenix can make good
> > use
> > > of both of them, should they choose to accept ownership of the code.
> > >
> > > On Wed, Oct 23, 2019 at 11:26 AM Alan Gates 
> > wrote:
> > >
> > > > Justin and mentors of Omid and Tephra,
> > > >
> > > > As Justin noted in his emails to these podlings this month both are
> > very
> > > > low activity, struggling to even file their reports, and appear to be
> > > > candidates for retirement.
> > > >
> > > > The situation here is somewhat special because Phoenix uses one or
> both
> > > of
> > > > these technologies (they are both transaction managers on top of
> > HBase),
> > > so
> > > > they may have an interest in their continued survival.  Tephra
> briefly
> > > > discussed this last June[1], though nothing came of it.  My
> conclusion
> > is
> > > > there is not enough momentum left for these podlings to vote
> themselves
> > > > into Phoenix without an external push.
> > > >
> > > > So before we push them into retirement I believe we should involve
> the
> > > > Phoenix PMC and see if they want to adopt either or both of these,
> with
> > > the
> > > > knowledge that they will likely be getting minimal contributions from
> > > > current members of those projects going forward.  If others are ok
> with
> > > > this I can contact the Phoenix PMC and see if they wish to take any
> > > action
> > > > on this.
> > > >
> > > > Alan.
> > > >
> > > > 1.
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>

Omid and Tephra

[Alan Gates]

Justin and mentors of Omid and Tephra,

As Justin noted in his emails to these podlings this month both are very
low activity, struggling to even file their reports, and appear to be
candidates for retirement.

The situation here is somewhat special because Phoenix uses one or both of
these technologies (they are both transaction managers on top of HBase), so
they may have an interest in their continued survival.  Tephra briefly
discussed this last June[1], though nothing came of it.  My conclusion is
there is not enough momentum left for these podlings to vote themselves
into Phoenix without an external push.

So before we push them into retirement I believe we should involve the
Phoenix PMC and see if they want to adopt either or both of these, with the
knowledge that they will likely be getting minimal contributions from
current members of those projects going forward.  If others are ok with
this I can contact the Phoenix PMC and see if they wish to take any action
on this.

Alan.

1.
https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E

Re: [VOTE] Release Apache Superset (incubating) 0.34.1 [RC2]

[Alan Gates]

+1.  Checked the LICENSE, NOTICE, and DISCLAIMER files.  Checked to see
there weren't any binary files and that all the code files had AL headers.

Alan.

On Mon, Oct 7, 2019 at 8:08 AM Ville Brofeldt 
wrote:

> Dear IPMC,
>
> The Apache Superset community has voted on and approved a proposal to
> release Apache Superset (incubating) 0.34.1 (rc2). This is a bug-fix
> release to the inaugural Apache release of Superset in August 2019.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Superset (incubating) is a business intelligence web application
>
> The community voting thread can be found here (3 binding +1
> votes):
> https://lists.apache.org/thread.html/e60f080ebdda26896214f7d3d5be1ccadfab95d48fbe813252762879@%3Cdev.superset.apache.org%3E
>
> The release candidate has been tagged in GitHub as tag 0.34.1rc2
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.34.1rc2
>
> The artifacts to be voted on are located
> here:https://dist.apache.org/repos/dist/dev/incubator/superset/
>
> Release artifacts are signed with the key located
> here:https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Superset (incubating) 0.15.1
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache
> Superset community to validate this release.
>
> On behalf of the Apache Superset Community,
>
> Ville
>

Re: [VOTE] Recommend 'Apache SINGA graduation to Top Level Project' resolution to the board

[Alan Gates]

>From one of the mentors, +1.  And congratulations to the Singa project!

Alan.

On Fri, Sep 13, 2019 at 1:38 PM Moaz Reyad  wrote:

> In the four and a half years that Apache SINGA (incubating) has been
> a part of the Apache incubator, the community has grown, diversified,
> and adapted to the Apache Way. We believe that the project is ready
> to graduate to a TLP.
>
> As a community, we have discussed [1] and voted [2] to graduate to a
> TLP, we have worked through the maturity model [3], notified the IPMC
> that we have the intention to graduate [4] and proposed PMC chair [5].
> We filed a software grant [6] and discussed the graduation here [7].
>
> Please take a minute to vote on whether or not the IPMC should recommend
> the resolution below to the Board by responding with one of the following:
>
> [ ] +1 Apache SINGA should graduate
> [ ]  0 No opinion
> [ ] -1 Apache SINGA should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> Thank you,
> Moaz, on behalf of Apache SINGA (incubating) community
>
> [1]
>
> https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
> [3]
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> [4]
>
> https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
> [5]
>
> https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E
> [6]
>
> https://lists.apache.org/thread.html/0ae459aa462ab1aac6771f6ce7ff2a8a14ac286103bee5e1a42426b2@%3Cprivate.singa.apache.org%3E
> [7]
>
> https://lists.apache.org/thread.html/8f4bbc5f2945ffcda848fcf5cf2f6ff676069e0807cef3221f401728@%3Cgeneral.incubator.apache.org%3E
>
> --
>
> Proposed Resolution for the Apache SINGA project for the ASF Board:
>
> Establish the Apache SINGA Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a distributed deep learning platform.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache SINGA Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache SINGA Project be and hereby is
> responsible for the creation and maintenance of software
> related to a distributed deep learning platform;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache SINGA" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache SINGA Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache SINGA Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache SINGA Project:
>
> * Thejas Nair ( the...@apache.org )
> * Alan Gates ( ga...@apache.org )
> * Ted Dunning ( tdunn...@apache.org )
> * Beng Chin Ooi ( oo...@apache.org )
> * Wang Wei ( wang...@apache.org )
> * Anh Dinh ( dinh...@apache.org )
> * Chen Gang( c...@apache.org )
> * Jinyang Gao ( jiny...@apache.org )
> * Kian-Lee Tan ( tankian...@apache.org )
> * Luo Zhaojing ( zhaoj...@apache.org )
> * Xie Zhongle ( zhon...@apache.org )
> * Zheng Kaiping ( kaip...@apache.org )
> * Moaz Reyad ( m...@apache.org )
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wang Wei
> be appointed to the office of Vice President, Apache SINGA, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache SINGA PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache SINGA Project; and be it further
>
> RESOLVED, that the Apache SINGA Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator SINGA podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator SINGA podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Alan Gates]

Ok, now that the SGA is filed, I'm +1 on this.  Thanks for chasing this
down.

Alan.

On Thu, Sep 5, 2019 at 2:36 AM Beng Chin OOI  wrote:

>
> A number have joined Alibaba, Kyoto University, Zhejiang University and
> other companies in
> various countries,  and some still continue to contribute.
>
> On Singapore side, IMDA https://www2.imda.gov.sg  is pushing the system
> for adoption by
> the local industry/SME.
>
> SINGA-lite (with federated learning facility, for edge computing etc)
> and SINGA-easy (for
> the dummies, such as clinicians and subject matter experts who are not
> AI experts) are on
> schedule for releases in three months time.
>
> regards
> beng chin
>
>
> On 2019-09-05 17:22, Justin Mclean wrote:
> > Hi,
> >
> >> 1. The affiliation of the proposed PMC can be found here [1]. It shows
> >> that
> >> the PPMC members belong to six different organizations (not counting
> >> the
> >> affiliations of the mentors)
> >
> > Thanks for that I can see that 1/2 are from the National University of
> > Singapore, would the project continue if for some some reason they
> > stopped contributing?  We’ve had several projects suddenly stop when a
> > majority of participants have moved elsewhere for one reasons or
> > another. This is probably not a blocker but something for teh project
> > to think out and perhaps try to increase the number of PMC members.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Alan Gates]

If I understand correctly, anytime software is brought into Apache as part
of the incubating process there must be documentation from the previous
owner of that software stating that they are donating it to Apache.
Without that Apache's ownership of the code is not clear.  Justin, Dave,
others, please correct me if this understanding is wrong.

And clearly there was code imported into Apache when Singa entered the
incubator, since an existing github link (now defunct) is referenced in
Singa's incubator proposal[1].

So I don't believe that an affirmation from PPMC that no docs are necessary
is sufficient.  I believe we need a code grant from whoever owned that code
previously.

Alan.

1. https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal see
the section on initial source.

On Mon, Sep 2, 2019 at 12:29 AM Justin Mclean  wrote:

> Hi,
>
> > The PPMC reached a conclusion on the discussion [1] that there is no need
> > for SGA.
>
> The link referred to doesn't give a reason why one is not required. Why
> was it decided that it wasn’t needed? Even if it not required (which I’m
> not 100% sure that is the case), would it be difficult to get one? If so
> why is that?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Alan Gates]

Yes, I saw that, but I can't find those papers.  They should have been
filed by the Apache secretary on the page I referenced.  Either they were
properly transferred and we need to find them so that they are properly
posted in case anyone ever needs them, or, if they weren't sent, then we
need to make sure a copy of them is sent.

I guess the next step is to email the secretary and ask if he's aware of
that transfer having taken place, unless anyone knows somewhere else I
should be looking for them.

Alan.

On Sat, Aug 31, 2019 at 3:48 AM Moaz Reyad  wrote:

> Dear Alan,
>
> The copyright section in the project page [1] has the following item :
>
> Date: 2015-03-31
> Item: Check and make sure that the papers that transfer rights to the ASF
> been received. It is only necessary to transfer rights for the package, the
> core code, and any new code produced by the project.
>
> I believe this answers your question about the transfer rights of the code.
> Please let me know if there is anything else required.
>
> We will proceed to vote if no one objects.
>
> Thank you,
> Moaz
>
> [1] http://incubator.apache.org/projects/singa.html
>
> On Tue, Aug 27, 2019 at 8:48 PM Alan Gates  wrote:
>
> > Sorry, I brought this up earlier on the dev list but didn't follow up.  I
> > can't find a copy of the code grant for the code that Singa brought into
> > the Incubator.  When I look at the Secretary's page[1] that lists all of
> > the code grants I don't see one for Singa.  Per the initial proposal[2]
> > there was code imported from an existing github repo [3], which means we
> > need to have a code grant from whom ever owned that code (National
> > University of Singapore would be my guess).
> >
> > We need to clear this up before Singa graduates to assure that the ASF
> has
> > the right to this code.
> >
> > Alan.
> >
> > [1] https://incubator.apache.org/ip-clearance/index.html
> > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal
> > [3] https://github.com/nusinga/singa
> >
> > On Tue, Aug 27, 2019 at 1:34 AM Moaz Reyad  wrote:
> >
> > > Hi all,
> > >
> > > In the four and a half years that Apache SINGA (incubating) has
> > > been a part of the Apache incubator, the community has grown,
> > diversified,
> > > and adapted to the Apache Way. We believe that the project is ready to
> > > graduate to a TLP.
> > >
> > > As a community, we have discussed [1] and voted [2] to graduate to a
> > > TLP, we have worked through the maturity model [3], notified the IPMC
> > that
> > > we have the intention to graduate [4] and proposed PMC chair [5].
> > >
> > > Please see the draft resolution appended below and provide any
> > > comments or feedback you have on it.
> > >
> > > We would like to continue the graduation process and hereby ask you
> > > all for your opinion on this. The discussion is open for 72 hours,
> after
> > > which we will start a [VOTE] on graduation here.
> > >
> > > Thanks,
> > >
> > > --moaz
> > > on behalf of the Apache SINGA PPMC
> > >
> > > [1]
> > >
> > >
> >
> https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
> > > [2]
> > >
> > >
> >
> https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
> > > [3]
> > >
> >
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> > > [4]
> > >
> > >
> >
> https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
> > > [5]
> > >
> > >
> >
> https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E
> > >
> > > Proposed Resolution for the Apache SINGA project for the ASF Board:
> > >
> > > X. Establish the Apache SINGA Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best
> > > interests of the Foundation and consistent with the
> > > Foundation's purpose to establish a Project Management
> > > Committee charged with the creation and maintenance of
> > > open-source software, for distribution at no charge to
> > > the public, related to a distributed deep learning platform.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Alan Gates]

Sorry, I brought this up earlier on the dev list but didn't follow up.  I
can't find a copy of the code grant for the code that Singa brought into
the Incubator.  When I look at the Secretary's page[1] that lists all of
the code grants I don't see one for Singa.  Per the initial proposal[2]
there was code imported from an existing github repo [3], which means we
need to have a code grant from whom ever owned that code (National
University of Singapore would be my guess).

We need to clear this up before Singa graduates to assure that the ASF has
the right to this code.

Alan.

[1] https://incubator.apache.org/ip-clearance/index.html
[2] https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal
[3] https://github.com/nusinga/singa

On Tue, Aug 27, 2019 at 1:34 AM Moaz Reyad  wrote:

> Hi all,
>
> In the four and a half years that Apache SINGA (incubating) has
> been a part of the Apache incubator, the community has grown, diversified,
> and adapted to the Apache Way. We believe that the project is ready to
> graduate to a TLP.
>
> As a community, we have discussed [1] and voted [2] to graduate to a
> TLP, we have worked through the maturity model [3], notified the IPMC that
> we have the intention to graduate [4] and proposed PMC chair [5].
>
> Please see the draft resolution appended below and provide any
> comments or feedback you have on it.
>
> We would like to continue the graduation process and hereby ask you
> all for your opinion on this. The discussion is open for 72 hours, after
> which we will start a [VOTE] on graduation here.
>
> Thanks,
>
> --moaz
> on behalf of the Apache SINGA PPMC
>
> [1]
>
> https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
> [3]
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> [4]
>
> https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
> [5]
>
> https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E
>
> Proposed Resolution for the Apache SINGA project for the ASF Board:
>
> X. Establish the Apache SINGA Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a distributed deep learning platform.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache SINGA Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache SINGA Project be and hereby is
> responsible for the creation and maintenance of software
> related to a distributed deep learning platform;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache SINGA" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache SINGA Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache SINGA Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache SINGA Project:
>
> * Thejas Nair ( the...@apache.org )
> * Alan Gates ( ga...@apache.org )
> * Ted Dunning ( tdunn...@apache.org )
> * Beng Chin Ooi ( oo...@apache.org )
> * Wang Wei ( wang...@apache.org )
> * Anh Dinh ( dinh...@apache.org )
> * Chen Gang( c...@apache.org )
> * Jinyang Gao ( jiny...@apache.org )
> * Kian-Lee Tan ( tankian...@apache.org )
> * Luo Zhaojing ( zhaoj...@apache.org )
> * Xie Zhongle ( zhon...@apache.org )
> * Zheng Kaiping ( kaip...@apache.org )
> * Moaz Reyad ( m...@apache.org )
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wang Wei
> be appointed to the office of Vice President, Apache SINGA, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache SINGA PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in th

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC2]

[Alan Gates]

+1.

Alan.

On Fri, Aug 23, 2019 at 12:56 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Hi IPMC,
>
> The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1
> recently, only to realize that there's was a minor blocking. The blocker
> was that the version was labelled `0.34.0rc1` inside the tarball, as
> opposed to `0.34.0`, meaning that when installing from source, the Python &
> npm packages would appear to be a `0.34.0rc1`. As you know, altering the
> tarball invalidates the MD5 / signature, so this is why we need this very
> minor tweak.
>
> 0.34.0rc2 addresses this, and uses `0.34.0` as the version number inside
> the tarball. I also addressed some of the [non-blocking] licensing comments
> surfaced during the RC1 process, and included the latest CHANGELOG in the
> tarball.
>
> Here are the 3 commits on top of RC1:
> 20e68c87 (HEAD -> 0.34, tag: 0.34.0rc2, origin/0.34, apache/0.34) Set
> version to 0.34.0 (no rcN)
> 6acd25d1 fix: minor release/license related issues (#8087)
> a13fb1d2 CHANGELOG for 0.30...0.34 (#8089)
>
> *This would be the first Apache release of Superset.*
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a business intelligence web application
>
> The community voting thread (for RC1) can be found here:
>
> https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E
>
> The release candidate has been tagged in GitHub as tag 0.34.0rc2
> ,
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/superset/
>
> Release artifacts are signed with the key located here:
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Superset (incubating)
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> community to validate this release.
>
> On behalf of the Apache Superset Community,
>
> Max
>
> 
>
> Apache Superset (incubating) is an effort undergoing incubation at The
> Apache
> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Alan Gates]

I would call a revote over that, it's not like you're changing anything of
import.  I'd just regen the package with the change, create the new hash,
and let everyone know.  I don't see any reason to drag back through the
voting process on two lists over this.

Alan.

On Wed, Aug 21, 2019 at 10:43 PM Justin Mclean 
wrote:

> Hi,
>
> > Oh here's something. Somewhere inside the source release I have a version
> > string that says "0.34.0rc1" and that now I'm realizing should really say
> > "0.34.0" as it becomes an official release. Now changing that string will
> > make for a different SHA.
>
> That's a bit awkward. It would be best to call a vote again if it needs to
> be changed, given the changes shod be minor it shod be easy to review.
>
> Other IPMC members might have another view. Anyone?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Alan Gates]

Forwarding my +1 from the dev list.  I checked the LICENSE, NOTICE, and
DISCLAIMER files, as well as looking over the contents of the release for
licenses and to make sure there weren't any binary files (beyond image
files).

Alan.

On Sun, Aug 18, 2019 at 9:41 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Hi IPMC,
>
> The Apache Superset community has voted on and approved a proposal to
> release
> Apache Superset (incubating) 0.34.0 (rc1). *This would be the first Apache
> release of Superset.*
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a business intelligence web application
>
> The community voting thread can be found here:
>
> https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E
>
> The release candidate has been tagged in GitHub as tag 0.34.0rc1
> ,
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.34.0rc1
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/superset/
>
> Release artifacts are signed with the key located here:
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Superset (incubating) 0.15.1
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> community to validate this release.
>
> On behalf of the Apache Superset Community,
>
> Max
>
> 
>
> Apache Superset (incubating) is an effort undergoing incubation at The
> Apache
> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>

Re: [VOTE] Release Apache Omid 1.0.1 (incubating)

[Alan Gates]

+1.  Did a build with a clean mvn repo and profile for HBase-2, looked at
the LICENSE, NOTICE, and DISCLAIMER files, checked for any binary files in
the distribution, and ran rat.

Alan.

On Tue, May 7, 2019 at 11:56 AM la...@apache.org  wrote:

>  Transferring my +1 from the Omid dev list.
> On Sunday, May 5, 2019, 1:56:57 AM EDT, Yoni Gottesman <
> yon...@apache.org> wrote:
>
>  The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 1.0.1-incubating.
>
> PPMC Vote Call:
> https://mail-archives.apache.org/mod_mbox/omid-dev/201905.mbox/%3CCAFWCdOqa0yC8yPhF26BG0fX5_guWEV2h3%2B9n2KxRf1CPePVtUA%40mail.gmail.com%3E
>
> PPMC Vote Result:
> https://mail-archives.apache.org/mod_mbox/omid-dev/201905.mbox/%3CCAAF1Jdi41sWKTfy6%2B-FY3JA8NHQcqJ17-fNB_sW%3DZOuOKph%2Bmg%40mail.gmail.com%3E
>
> PPMC Vote Summary:
> 4 binding (IPMC member) +1 votes
> 0 non-binding PPMC member +1 votes
> No -1 votes
>
> Git tag for the
> release:
> https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git;a=tag;h=aca4d171b12cc18b8cd482e5f2411b86be1b17e5
>
> Sources for the
> release:
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz
>
> Source release verification:
>   PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz.asc
>
>   SHA512 Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz.sha512
>
>
>   Keys to verify the signature of the release artifact are available
> at:https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/KEYS
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Omid 1.0.1-incubating. Please try out the package and vote.
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache Omid 1.0.1-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add (binding) if your vote is binding.
>

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

[Alan Gates]

Forwarding my +1 from the dev list.  Checked the NOTICE, LICENSE, and
DISCLAIMER files.  Did a quick check that everything had appropriate Apache
License headers, and I didn't find any binaries in the RC.

Alan.

On Wed, Apr 24, 2019 at 1:37 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.32.0 RC2 for Apache Superset is baked and available
> at:
> https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> keys are available
> at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This is the second ASF release candidate of Superset (!)* We're still
> ironing out our release process, so please bear with us and help if you
> can*
> .
>
> Here's link to original successful VOTE thread on dev@:
>
> http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E
>
> As I went along, I documented the process in RELEASING.md in the repo,
> latest edits here https://github.com/apache/incubator-superset/pull/7329
>
> For context (and similarly to 0.31) the `0.32` release branch was cut at
> SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common
> ancestor, the following list of commit was added as cherry-picks. The SHAs
> in the list bellow reference the cherries on the release branch, PR number
> are available to get more details.
>
> New commits since 0.32.0rc1 *in bold:*
>
> *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2*
> *3e6f6848 Add disclaimer and remove counter (#6738)*
> c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1
> b89cdbdc RELEASING.md from master
> 0e23f2e6 Add sign.sh
> 21804346 [load_examples] download data at runtime (#7314)
> b32d5900 Remove LICENSE entry around dataset (#7318)
> b3aa5633 (release--0.31) 0.31rc23
> 24a595f4 bugfix: improve 'Time Table' (#6959)
> c70abbed 0.31rc22
> dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198)
> (#7242)
> a9d54894 0.31.0rc21
> b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal
> (#7179)
> 2da9613f Update __init__.py (#7166)
> 538da2e3 0.31.0.rc20
> 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145)
> 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144)
> daf2b8e5 Bump python lib croniter to an existing version (#7132)
> eb4c1355 Use metric name instead of metric in filter box (#7106)
> 2ff721ae handle null column_name in sqla and druid models
> e83a07d3 [forms] Fix handling of NULLs
> 76d26f37 0.31.0.rc19
> fe78b4ec Fix filter_box migration PR #6523 (#7066)
> c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query
> (#7029)
> b64a452a [sql lab] improve table name detection in free form SQL (#6793)
> 2357c4aa Adding custom control overrides (#6956)
> 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963)
> 5d8dd142 [csv-upload] Fixing message encoding (#6971)
> f454dedd [main] Disable resetting main DB attributes (#6845)
> e967b268 [sqla] Fixing order-by for non-inner-joins (#6862)
> a5d9a4e0 Adding template_params to datasource editor for sqla tables
> (#6869)
> 6b895413 [datasource] Ensuring consistent behavior of datasource
> editing/saving. (#7037)
> 8ef2789f Adding warning message for sqllab save query (#7028)
> 0ebdb564 fix inaccurate data calculation with adata rolling and
> contribution (#7035)
> b3af6a26 [fix] explore chart from dashboard missed slice title (#7046)
> c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007)
> bd65942e Changing time table viz to pass formatTime a date (#7020)
> 50accda9 [fix] Cursor jumping when editing chart and dashboard titles
> (#7038)
> 5ace5769 0.31.0rc17
> 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on
> refresh (#7027)
> fafb824d 0.31.0rc16
> 7b72985e [fix] /superset/slice/id url is too long (#6989)
> b497d9e7 fix dashboard links in welcome page (#6756)
> c42afa11 0.31.0rc15
> 35c55278 Enhancement of query context and object. (#6962)
> 1c41020c Split tags migration (#7002)
> ec7a0b22 0.31.0rc14
> 4655cb4c Remove Cypress from package.json (#6912)
> fb8e3208 0.31.0rc13
> b4cbe13d VIZ-190 fix (#6958)
> 5b7b22fd 0.31.0rc12
> 51804229 Fix deck.gl form data (#6953)
> 9939a52d 0.31.0rc11
> c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix
> rendering regression from the introduction of bignumber (#6937)
> 9940d30a 0.31.0rc10
> 3df2b8d5 Add a safety check before getting clientHeight (#6923)
> ccb51385 v0.31.0rc9
> db0235fb Fix database typeahead in SQL Lab (#6917)
> 953d6dc9 Address tooltip's disappearance and stickiness (#6898)
> c0eaa5f6 Fix extra_filters in multi line viz (#6868)
> ebcadc1f (apache/cherry_ebcadc1f50994d98bd3dc42e2199b8d0328c061c) Fix
> tooltip (#6895)
> 5fa5acb5 Add show metadata button back to the explore view (#6911)
> ce76560a v0.31.0rc8
> 8c549b46 Relayout SQL Editor (#6872)
> bfe18963 

Re: [VOTE] Release apache-singa-incubating-2.0.0 (RC1)

[Alan Gates]

Forwarding my +1 from the dev list.  Checked signatures, sha, did a quick
check to make sure files without headers were referenced in LICENSE or
NOTICE, looked for binary files in the distribution.

Alan.

On Wed, Apr 10, 2019 at 6:21 PM Chonho Lee  wrote:

> Hi all,
>
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 2.0.0 (incubating).
>
> The vote thread is at:
>
> http://mail-archives.apache.org/mod_mbox/singa-dev/201904.mbox/%3CCADVfyeuVVE6SZe_%2B6A5OpApY5rDRhBWCfv8H1uZ%2BZuz1NR17_g%40mail.gmail.com%3E
>
> and the result is at:
>
> http://mail-archives.apache.org/mod_mbox/singa-dev/201904.mbox/%3CCADVfyeuUBih-sdopzPSp3%2BgS1%3DMYaL-7zjjqkBmGaxkbgLeLYw%40mail.gmail.com%3E
>
> We ask the IPMC to vote on this release.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/singa/2.0.0/
>
> The hashes of the artifacts are as follows:
> SHA512: D422ED7C 1AD370CA 66D5591B E581DC3C 2513396E 465CF983 80785929
> A70189AA 8944452A 1B10AF23 03F781BF 5D4066CE D994FE97 123280A1 EA34A681
> 3402BA12
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dinhtta.asc
>
> and the signature file is:
>
> https://dist.apache.org/repos/dist/dev/incubator/singa/2.0.0/apache-singa-incubating-2.0.0-RC1.tar.gz.asc
>
>
> The Github tag is at:
> https://github.com/apache/incubator-singa/releases/tag/2.0.0rc1
> commit ID is: 5f14f3dbc005a64fdbc508bff63db92e6d3e05b6
>
> To check the license, you can use the Apache Rat tool as follows:
> 1. download & decompress apache rat from
> http://creadur.apache.org/rat/download_rat.cgi
> 2. run the following command under singa folder:
> java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> rat_check
> 3. check the results in file named "rat_check"
>
> Please check and vote on releasing this package. The vote is open for at
> least 72 hours and passes if a majority of at least three +1 votes are
> cast.
>
> [ ] +1 Release this package as Apache SINGA 2.0.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Here is my vote:
> +1 (non-binding)
>
> Best,
>
> --
> Chonho Lee
>

Podling use of StackOverflow

[Alan Gates]

The superset podling is working out their processes around FAQs and
answering user questions.  One thing that they have suggested is that they
encourage people to use StackOverflow for questions and answers given the
ease of searching old questions, etc.  You can see the mail thread at
https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E

Personally I think encouraging podlings to use tools they and everyone are
comfortable with and that meet our criteria of being open to all is a good
thing, but I wanted to check if there was official policy on this before
they proceed with it.

Alan.

Re: Does a new podling committer require notice to the IPMC?

[Alan Gates]

Thanks Hitesh.

Alan.

On Thu, Dec 20, 2018 at 4:30 PM Hitesh Shah  wrote:

> The notice is only for new PPMC members. Most podlings do not differentiate
> between committers and PPMC so you would end up seeing notice emails for
> new committers being sent to the IPMC.
>
> https://incubator.apache.org/guides/ppmc.html#voting_in_a_new_ppmc_member
>
> Hitesh
>
>
> On Thu, Dec 20, 2018 at 3:13 PM Alan Gates  wrote:
>
> > We used to require that a podling notify the IPMC after its PPMC had
> voted
> > to invite a contributor to be a committer and before the candidate was
> > notified.  Do we still require that? I can't recall seeing any emails
> from
> > other podlings on that lately and I couldn't find any docs on the
> incubator
> > site one way or another.
> >
> > Alan.
> >
>

Does a new podling committer require notice to the IPMC?

[Alan Gates]

We used to require that a podling notify the IPMC after its PPMC had voted
to invite a contributor to be a committer and before the candidate was
notified.  Do we still require that? I can't recall seeing any emails from
other podlings on that lately and I couldn't find any docs on the incubator
site one way or another.

Alan.

Re: [VOTE] Release Apache Omid 1.0.0 (incubating)

[Alan Gates]

+1.  Did a build with a clean mvn repo, checked the DISCLAIMER, NOTICE, and
LICENSE files.  Found the RAT issues already noted by Josh.  Getting these
fixed soon would be good as finding license issues is much harder by hand
then with RAT.

Alan.

On Tue, Nov 27, 2018 at 1:15 PM Josh Elser  wrote:

> +1 (binding)
>
> The RAT plugin fails but these look fine to fix for the next release:
>
> Unapproved licenses:
>
>.travis.yml
>bintray-settings.xml
>misc/findbugs-exclude.xml
>misc/omid_checks.xml
>
> Everything else looks good to me.
>
> On 11/18/18 2:45 AM, Ohad Shacham wrote:
> > Hi,
> >
> >
> > The Apache Omid community has voted on and approved a proposal
> > to release Apache Omid 1.0.0-incubating.
> >
> > PPMC Vote Call:
> http://mail-archives.apache.org/mod_mbox/omid-dev/201811.mbox/%3ccahuxfymp-_qvcn2qde3bqcqdta3hwbwfa52ygtuqr64qkjk...@mail.gmail.com%3e
> >
> >
> > PPMC Vote Result:
> >
> >
> http://mail-archives.apache.org/mod_mbox/omid-dev/201811.mbox/%3cCAAF1JdinF60+hsxHbvxcx3oDruGqoE7BJ=gh_EbadFbDRHm8=w...@mail.gmail.com%3e
> >
> >
> > PPMC Vote Summary:
> > 4 binding (IPMC member) +1 votes
> > 0 non-binding PPMC member +1 votes
> > No -1 votes
> >
> > Release notes for the 1.0.0 release:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/RELEASE_NOTES.html
> >
> >
> > Git tag for the release:
> >
> >
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?p=incubator-omid.git;a=tag;h=14d5cb2d899ef381be40edc6d95aede50bb396ea
> >
> >
> > Sources for the release:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz
> >
> >
> >
> > Source release verification:
> >
> >
> > PGP Signature:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.asc
> >
> > SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifact are available
> > at:https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/KEYS
> >
> >
> > We request the permission of IPMC to publish the above release candidate
> as
> > Apache Omid 1.0.0-incubating. Please try out the package and vote. The
> vote
> > is open for a minimum of 72 hours or until the necessary number of votes
> (3
> > binding +1s) is reached. [ ] +1 Release this package as Apache Omid
> > 1.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with
> > the release [ ] -1 Do not release this package because... Please add
> > (binding) if your vote is binding.
> >
> >
> > Thanks,
> > Ohad and Yoni
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache HAWQ (incubating)

[Alan Gates]

+1.

Alan.

On Fri, Jul 27, 2018 at 7:13 PM Roman Shaposhnik  wrote:

> Hi!
>
> after a very positive discussion in the HAWQ community
> and at the IPMC level:
>
> https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193cc110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E
>
> https://lists.apache.org/thread.html/3a142d758ef5ae119e421071893615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E
>
> I'd like to bring the following resolution for a formal vote.
>
> Please vote on the resolution pasted below to graduate
> Apache HAWQ from the incubator to top level project.
>
> [ ] +1 Graduate Apache HAWQ from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache HAWQ from the Incubator because...
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache HAWQ PPMC).
>
> ## Resolution to create a TLP from graduating Incubator podling
>
> X. Establish the Apache HAWQ Project
>
>WHEREAS, the Board of Directors deems it to be in the best
>interests of the Foundation and consistent with the
>Foundation's purpose to establish a Project Management
>Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to
>the public, related to Hadoop native SQL query engine that
>combines the key technological advantages of MPP database
>with the scalability and convenience of Hadoop.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache HAWQ Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache HAWQ Project be and hereby is
>responsible for the creation and maintenance of software
>related to Hadoop native SQL query engine that
>combines the key technological advantages of MPP database
>with the scalability and convenience of Hadoop;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache HAWQ" be
>and hereby is created, the person holding such office to
>serve at the direction of the Board of Directors as the chair
>of the Apache HAWQ Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache HAWQ Project; and be it further
>
>    RESOLVED, that the persons listed immediately below be and
>hereby are appointed to serve as the initial members of the
>Apache HAWQ Project:
>
> * Alan Gates   
> * Alexander Denissov   
> * Amy Bai  
> * Atri Sharma  
> * Bhuvnesh Chaudhary   
> * Bosco
> * Chunling Wang
> * David Yozie  
> * Ed Espino
> * Entong Shen  
> * Foyzur Rahman
> * Goden Yao
> * Gregory Chase
> * Hong Wu  
> * Hongxu Ma
> * Hubert Zhang 
> * Ivan Weng
> * Jesse Zhang  
> * Jiali Yao
> * Jun Aoki 
> * Kavinder Dhaliwal
> * Lav Jain 
> * Lei Chang
> * Lili Ma  
> * Lirong Jian  
> * Lisa Owen
> * Ming Li  
> * Mohamed Soliman  
> * Newton Alex  
> * Noa Horn 
> * Oleksandr Diachenko  
> * Paul Guo 
> * Radar Da Lei 
> * Roman Shaposhnik 
> * Ruilong Huo  
> * Shivram Mani 
> * Shubham Sharma   
> * Tushar Pednekar  
> * Venkatesh Raghavan   
> * Vineet Goel  
> * Wen Lin  
> * Xiang Sheng  
> * Yi Jin   
> * Zhanwei Wang 
> * Zhenglin Tao 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lei Chang
>be appointed to the office of Vice President, Apache HAWQ, to
>serve in accordance with and subject to the direction of the
>Board of Directors and the Bylaws of the Foundation until
>death, resignation, retirement, removal or disqualification,
>or until a successor is appointed; and be it further
>

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

[Alan Gates]

+1.  Did a build in a fresh repo, looked over the LICENSE and NOTICE files,
ran rat.  Rat initially fails, but on further inspection all the files it's
complaining about are the other license files.  I believe there's a way to
exclude these files from the rat run.  In the future it would be good to
clean those up so that it's easy to see whether rat passes or fails.

On Wed, May 23, 2018 at 3:57 PM Joe Witt  wrote:

> +1 (binding)
>
> Verified source bundle signature and hashes and disclaimer.
> Verified build and distribution artifact (no live testing).
>
> Tephra release vote findings/improvements for consideration:
> 1) Use of md5 hashes worth removing in future releases
> 2) Copyright year in source and binary notice
> 3) I dont believe category B (for example the EPL dependencies in
> binary license) dependencies belong in the license (binary or
> otherwise).  https://www.apache.org/legal/resolved.html#category-b
>   It is my understanding those would be reflected in the notice.
> 4) There are a number of binary dependencies in the lib folder of the
> tephra distribution artifact that are not called out in the
> license/notice. These include ASF projects.  Should review these for
> inclusion. The ASF projects might not need a mention but they often
> have NOTICE files and those usually need to be carried forward as well
> - ASF projects also have copyrights that might need to be carried over
> as well. Commons lang has an interesting line worth considering for
> inclusion https://github.com/apache/commons-lang/blob/master/NOTICE.txt
>
> On Tue, May 22, 2018 at 2:01 AM, Jitendra Pandey
>  wrote:
> > +1 (binding)
> > Verified md5 of the source tarball.
> > Downloaded source, built successfully, ran a few unit tests.
> >
> > On 5/21/18, 9:02 PM, "Josh Elser"  wrote:
> >
> > +1 (binding)
> >
> > Things look good for the most part, a few things I noticed which can
> be
> > fixed next release:
> >
> > * NOTICE needs an updated copyright year
> > * `mvn apache-rat:check` fails on the below files
> >
> > 
> > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL
> > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD
> >
>  apache-tephra-0.14.0-incubating/tephra-distribution/licenses/JLine.BSD
> >
>  apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Logback.EPL
> > apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY
> > 
> >
> > On 5/21/18 6:51 PM, James Taylor wrote:
> > > Hi all,
> > >
> > > This is a call for a vote on releasing Apache Tephra
> 0.14.0-incubating,
> > > release candidate 1. This is the seventh release of Tephra. The
> Tephra dev
> > > community has voted on and approved a proposal to release Tephra
> > > 0.14.0-incubating, release candidate 1.
> > >
> > > PPMC Vote Call: https://s.apache.org/jWVD
> > >
> > > PPMC Vote Result: https://s.apache.org/zwog
> > >
> > > The source tarball, including signatures, digests, etc. can be
> found at:
> > >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/src
> > >
> > > The tag to be voted upon is v0.14.0-incubating:
> > >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.14.0-incubating
> > >
> > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
> > >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
> > >
> > > The Nexus Staging URL:
> > >
> https://repository.apache.org/content/repositories/orgapachetephra-1011
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/keys/committer/jamestaylor
> > >
> > > KEYS file available:
> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> > >
> > > For information about the contents of this release, see:
> > >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt
> > >
> > > Please vote on releasing this package as Apache Tephra
> 0.14.0-incubating
> > >
> > > The vote will be open for 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thanks,
> > > James
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

On Thu, Apr 12, 2018 at 9:52 AM, Matt Sicker  wrote:

> * Signatures ok
> * Disclaimer, license, notice ok
> * Rat check ok
>
> I am, however, getting a test failure:
>
> Failed tests:
>
> TestTSOClientConnectionToTSO.testSuccessOfTSOClientReconnec
> tionsToARestartedTSOWithZKPublishing:214
> » Execution
>   TestTSOClientConnectionToTSO.testSuccessfulConnectionToTSOThroughZK:176
> »
> Execution
>
> More details:
>
> Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 8.343 sec
> <<< FAILURE! - in org.apache.omid.tso.client.TestTSOClientConnectionToTSO
> testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPubl
> ishing(org.apache.omid.tso.client.TestTSOClientConnectionToTSO)
> Time elapsed: 1.738 sec  <<< FAILURE!
> java.util.concurrent.ExecutionException: java.net.NoRouteToHostException:
> No route to host
> at
> org.apache.omid.tso.client.TestTSOClientConnectionToTSO.
> testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing(
> TestTSOClientConnectionToTSO.java:214)
> Caused by: java.net.NoRouteToHostException: No route to host
>
> testSuccessfulConnectionToTSOThroughZK(org.apache.omid.tso.client.
> TestTSOClientConnectionToTSO)
> Time elapsed: 1.247 sec  <<< FAILURE!
> java.util.concurrent.ExecutionException: java.net.NoRouteToHostException:
> No route to host
> at
> org.apache.omid.tso.client.TestTSOClientConnectionToTSO.
> testSuccessfulConnectionToTSOThroughZK(TestTSOClientConnectionToTSO.
> java:176)
> Caused by: java.net.NoRouteToHostException: No route to host
>
>
> On 12 April 2018 at 05:54, Ohad Shacham  wrote:
>
> > Hi,
> >
> >
> > The Apache Omid community has voted on and approved a proposal
> > to release Apache Omid 0.9.0.0-incubating.
> >
> > PPMC Vote Call:http://mail-archives.apache.org/mod_mbox/incubator-
> > omid-dev/201804.mbox/%3cCAHuxFyN_uzAb12=AS-WyVXiwn1KTwmk2SY4=
> > b1f6zktwebu...@mail.gmail.com%3e
> >
> >
> > PPMC Vote Result:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-omid-
> dev/201804.mbox/%
> > 3cCAChRgeEQg7E-V6abZaWLaxiEdmULTtcmS_w=4v2d7oye0yf...@mail.gmail.com%3e
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-omid-
> dev/201804.mbox/%
> > 3cCAAF1JdhkMXvObfMD6xV=RPXhk9fg27fHR-kR6tAt=w1dweo...@mail.gmail.com%3e
> >
> >
> > PPMC Vote Summary:
> > 4 binding (IPMC member) +1 votes
> > 0 non-binding PPMC member +1 votes
> > No -1 votes
> >
> > Release notes for the 0.9.0.0
> > release:https://dist.apache.org/repos/dist/dev/incubator/
> > omid/0.9.0.0-rc2/RELEASE_NOTES.html
> >
> >
> > Git tag for the release:
> >
> > https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?
> > p=incubator-omid.git;a=tag;h=264a30e825bd0a75c435888d3cc12a35b19b4405
> >
> >
> > Sources for the release:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> > 0-rc2/apache-omid-incubating-0.9.0.0-src.tar.gz
> >
> >
> > Source release verification: PGP Signature:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> > 0-rc2/apache-omid-incubating-0.9.0.0-src.tar.gz.asc
> >
> >
> > SHA512 Hash:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> > 0-rc2/apache-omid-incubating-0.9.0.0-src.tar.gz.sha512
> >
> >
> > Keys to verify the signature of the release artifact are available at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc2/KEYS
> >
> >
> > We request the permission of IPMC to publish the above release candidate
> as
> > Apache Omid 0.9.0.0-incubating. Please try out the package and vote. The
> > vote is open for a minimum of 72 hours or until the necessary number of
> > votes (3 binding +1s) is reached. [ ] +1 Release this package as Apache
> > Omid 0.9.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm
> okay
> > with the release [ ] -1 Do not release this package because... Please add
> > (binding) if your vote is binding.
> >
> >
> > Thanks,
> > Ohad
> >
>
>
>
> --
> Matt Sicker 
>

Re: Two new Samoa committers

[Alan Gates]

When I got the email from root@apache it said:


Please grant additional karma to the projects in your domain
you wish the user to have commit to.

Only PMC chairs can grant karma.  If needed, please post to the general@/
dev@/private@ list of your project asking for someone with sufficient
karma to grant access to 'pwawrzyniak'.


If this is old and no longer applicable and there's nothing else to do,
then feel free to ignore my request.

Alan.

On Thu, Mar 22, 2018 at 4:07 PM, John D. Ament <johndam...@apache.org>
wrote:

> Alan,
>
> i'm not sure what karma you're looking for.  I just checked both accounts.
>
> - If samoa is using git-wip-us then they already have access as they are
> committers on incubator (this was likely done by secretary)
> - If samoa is using gitbox/github then they already have access as they are
> committers on samoa (this may have also been done by secretary)
>
> I checked https://whimsy.apache.org/roster/ppmc/samoa to confirm
> membership
> of both.  You (as well as the rest of the samoa PPMC) should have access to
> this page to manipulate the roster.
>
> Is there anything that they can't do?
>
> John
>
> On Thu, Mar 22, 2018 at 6:27 PM Alan Gates <alanfga...@gmail.com> wrote:
>
> > John, can you grant karma on Samoa to Piotr Wawrzyniak (pwawrzyniak) and
> > Maciej Grzenda (mgrzenda).  Both have recently been voted in as
> > committers.  Their id's have been created but I do not have power to
> grant
> > them karma.  Thanks.
> >
> > Alan.
> >
>

Two new Samoa committers

[Alan Gates]

John, can you grant karma on Samoa to Piotr Wawrzyniak (pwawrzyniak) and
Maciej Grzenda (mgrzenda).  Both have recently been voted in as
committers.  Their id's have been created but I do not have power to grant
them karma.  Thanks.

Alan.

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

On Thu, Mar 22, 2018 at 5:29 AM, Ohad Shacham 
wrote:

> Hi,
>
>
> The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 0.9.0.0-incubating.
>
> PPMC Vote Call:http://mail-archives.apache.org/mod_mbox/incubator-
> omid-dev/201803.mbox/%3c1827900384.321006.1520932655...@mail.yahoo.com%3e
>
>
> PPMC Vote Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-omid-dev/201803.mbox/%
> 3cCANQiJeVst7a9oSMKx9-m0=y6ypz9dnhxxytq6p5wegjnhwj...@mail.gmail.com%3e
>
>
> PPMC Vote Summary:
> 3 binding (IPMC member) +1 votes
> 1 non-binding PPMC member +1 votes
> No -1 votes
>
> Git tag for the release:
>
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?
> p=incubator-omid.git;a=tag;h=5dd5f86822beb43d08e91d00dd2427b4f130d6c2
>
>
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz
>
>
> Source release verification: PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz.asc
>
>
> MD5 Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz.md5
>
>
> Keys to verify the signature of the release artifact are available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc1/KEYS
>
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Omid 0.9.0.0-incubating. Please try out the package and vote. The
> vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached. [ ] +1 Release this package as Apache
> Omid 0.9.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay
> with the release [ ] -1 Do not release this package because... Please add
> (binding) if your vote is binding.
>
>
> Thanks,
> Ohad
>

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

Henk kindly pointed me to the KEYS file that I had missed, thank you.

So, +1.  I checked the signatures, the LICENSE, NOTICE, and DISCLAIMER
files.

Alan.

On Tue, Mar 13, 2018 at 10:42 AM, Alan Gates <alanfga...@gmail.com> wrote:

> Per https://www.apache.org/dev/release-distribution#sigs-and-sums
> correctly, the KEYS file is required, hence my comment.
>
> Alan.
>
> On Tue, Mar 13, 2018 at 10:34 AM, Henk P. Penning <penn...@uu.nl> wrote:
>
>> On Tue, 13 Mar 2018, Alan Gates wrote:
>>
>> Date: Tue, 13 Mar 2018 18:04:08 +0100
>>> From: Alan Gates <alanfga...@gmail.com>
>>> To: general@incubator.apache.org
>>> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>>>
>>> ​I can't find a KEYS file anywhere in HAWQ to check the key
>>> against.  There is also no name associated with the key, so I'm not
>>> clear how to check the signature.
>>>
>>
>>   Actually, you don't need a KEYS file to verify a .asc :
>>
>>   % gpg apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Can't check signature: No public key
>>
>>   No public key ; so, fetch it :
>>
>>   % gpg --keyserver pgp.surfnet.nl --recv-key CE60F90D1333092A
>>   gpg: requesting key CE60F90D1333092A from hkp server pgp.surfnet.nl
>>   gpg: key CE60F90D1333092A: public key "Yi Jin <y...@apache.org>"
>> imported
>>   gpg: Total number processed: 1
>>   gpg:   imported: 1  (RSA: 1)
>>
>>   ... and --verify :
>>
>>   % gpg --verify apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Good signature from "Yi Jin <y...@apache.org>"
>>   gpg: WARNING: This key is not certified with a trusted signature!
>>   gpg:  There is no indication that the signature belongs to the
>> owner.
>>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
>> 092A
>>
>>   % gpg --verify apache-hawq-rpm-2.3.0.0-incubating-rc2.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:38:53 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Good signature from "Yi Jin <y...@apache.org>"
>>   gpg: WARNING: This key is not certified with a trusted signature!
>>   gpg:  There is no indication that the signature belongs to the
>> owner.
>>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
>> 092A
>>
>>   Note :
>>   - Always use long (16-hex) key-id's, because short (8-hex)
>> key-id's often point (also) to fake keys.
>> In your $HOME/.gnupg/gpg.conf configure : keyid-format long
>>   - To check that CE60F90D1333092A is authorised to sign the artifacts,
>> is another matter.
>>
>>   IMHO, KEYS files serve no purpose.
>>
>>   Regards,
>>
>>   Henk Penning
>>
>>    _
>> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>>
>> On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik <ro...@shaposhnik.org>
>>> wrote:
>>>
>>> +1 (binding)
>>>>
>>>> * checked sigs and checksums
>>>> * checked licenses
>>>> * checked for archive matching git tag
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>>
>>>> On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik <c...@apache.org>
>>>> wrote:
>>>>
>>>>> +1 [biding]
>>>>>
>>>>> - signature check [ok]
>>>>> - checksum check [ok]
>>>>> - licenses check (RAT) [ok]
>>>>>
>>>>> I haven't tried to build it because of the complexity of the build
>>>>> process and multiplicity of the environment configurations. To lower
>>>>> the entry barrier, I would recommend the community to think how to
>>>>> wrap these steps into the build system. You can go as far as to
>>>>> provide an "official" toolchain for the project. In Bigtop, we even
>>>>> provide official Docker containers were 

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

Per https://www.apache.org/dev/release-distribution#sigs-and-sums
correctly, the KEYS file is required, hence my comment.

Alan.

On Tue, Mar 13, 2018 at 10:34 AM, Henk P. Penning <penn...@uu.nl> wrote:

> On Tue, 13 Mar 2018, Alan Gates wrote:
>
> Date: Tue, 13 Mar 2018 18:04:08 +0100
>> From: Alan Gates <alanfga...@gmail.com>
>> To: general@incubator.apache.org
>> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>>
>> ​I can't find a KEYS file anywhere in HAWQ to check the key
>> against.  There is also no name associated with the key, so I'm not
>> clear how to check the signature.
>>
>
>   Actually, you don't need a KEYS file to verify a .asc :
>
>   % gpg apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Can't check signature: No public key
>
>   No public key ; so, fetch it :
>
>   % gpg --keyserver pgp.surfnet.nl --recv-key CE60F90D1333092A
>   gpg: requesting key CE60F90D1333092A from hkp server pgp.surfnet.nl
>   gpg: key CE60F90D1333092A: public key "Yi Jin <y...@apache.org>"
> imported
>   gpg: Total number processed: 1
>   gpg:   imported: 1  (RSA: 1)
>
>   ... and --verify :
>
>   % gpg --verify apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Good signature from "Yi Jin <y...@apache.org>"
>   gpg: WARNING: This key is not certified with a trusted signature!
>   gpg:  There is no indication that the signature belongs to the
> owner.
>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
> 092A
>
>   % gpg --verify apache-hawq-rpm-2.3.0.0-incubating-rc2.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:38:53 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Good signature from "Yi Jin <y...@apache.org>"
>   gpg: WARNING: This key is not certified with a trusted signature!
>   gpg:  There is no indication that the signature belongs to the
> owner.
>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
> 092A
>
>   Note :
>   - Always use long (16-hex) key-id's, because short (8-hex)
> key-id's often point (also) to fake keys.
> In your $HOME/.gnupg/gpg.conf configure : keyid-format long
>   - To check that CE60F90D1333092A is authorised to sign the artifacts,
> is another matter.
>
>   IMHO, KEYS files serve no purpose.
>
>   Regards,
>
>   Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik <ro...@shaposhnik.org>
>> wrote:
>>
>> +1 (binding)
>>>
>>> * checked sigs and checksums
>>> * checked licenses
>>> * checked for archive matching git tag
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>>> On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik <c...@apache.org>
>>> wrote:
>>>
>>>> +1 [biding]
>>>>
>>>> - signature check [ok]
>>>> - checksum check [ok]
>>>> - licenses check (RAT) [ok]
>>>>
>>>> I haven't tried to build it because of the complexity of the build
>>>> process and multiplicity of the environment configurations. To lower
>>>> the entry barrier, I would recommend the community to think how to
>>>> wrap these steps into the build system. You can go as far as to
>>>> provide an "official" toolchain for the project. In Bigtop, we even
>>>> provide official Docker containers were people can start working with
>>>> the project in under 2 minutes and without any need for additional
>>>> error prone configuration steps.
>>>> --
>>>>   With regards,
>>>> Konstantin (Cos) Boudnik
>>>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>>>
>>>> Disclaimer: Opinions expressed in this email are those of the author,
>>>> and do not necessarily represent the views of any company the author
>>>> might be affiliated with at the moment of writing.
>>>>
>>>>
>>>> On Tue, Mar 6, 2018 a

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

​I can't find a KEYS file anywhere in HAWQ to check the key against.  There
is also no name associated with the key, so I'm not clear how to check the
signature.

Other than that release looks fine.​

On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik 
wrote:

> +1 (binding)
>
> * checked sigs and checksums
> * checked licenses
> * checked for archive matching git tag
>
> Thanks,
> Roman.
>
>
> On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik 
> wrote:
> > +1 [biding]
> >
> > - signature check [ok]
> > - checksum check [ok]
> > - licenses check (RAT) [ok]
> >
> > I haven't tried to build it because of the complexity of the build
> > process and multiplicity of the environment configurations. To lower
> > the entry barrier, I would recommend the community to think how to
> > wrap these steps into the build system. You can go as far as to
> > provide an "official" toolchain for the project. In Bigtop, we even
> > provide official Docker containers were people can start working with
> > the project in under 2 minutes and without any need for additional
> > error prone configuration steps.
> > --
> >   With regards,
> > Konstantin (Cos) Boudnik
> > 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> >
> > Disclaimer: Opinions expressed in this email are those of the author,
> > and do not necessarily represent the views of any company the author
> > might be affiliated with at the moment of writing.
> >
> >
> > On Tue, Mar 6, 2018 at 6:56 PM, Yi JIN  wrote:
> >> Hi IPMC members,
> >>
> >> The PPMC vote for the Apache HAWQ 2.3.0.0-incubating release has passed.
> >> So I request IPMC now to vote on this release candidate. Thank you!
> >>
> >> The release page is here:
> >> https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-
> incubating+Release
> >>
> >> The PPMC vote thread is located here:
> >> https://lists.apache.org/thread.html/fa5b41cd7461bd729146e10d8f7a54
> 156c818f93e5a1160c42e76c79@%3Cdev.hawq.apache.org%3E
> >>
> >> The artifacts can be downloaded here:
> >> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.
> 0-incubating.RC2/
> >> The artifacts have been signed with Key : CE60F90D1333092A
> >>
> >> All JIRAs completed for this release are tagged with 'FixVersion
> >> =2.3.0.0-incubating'
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12340262=Html=12318826
> >>
> >> Please vote accordingly:
> >> [ ] +1, accept as the official Apache HAWQ 2.3.0.0-incubating release
> >> [ ] -1, do not accept as the official Apache HAWQ 2.3.0.0-incubating
> release
> >> because...
> >>
> >> The vote will run for at least 72 hours.
> >>
> >> Best regards,
> >> Yi Jin (yjin)
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[Alan Gates]

​They have removed the LGPL code.  Not removing the license as well is an
oversight.

Alan.​

On Mon, Sep 18, 2017 at 5:08 PM, John D. Ament 
wrote:

> Hi,
>
> I'm inclined to vote -1 unless someone convinces me otherwise.
>
> TEPHRA-231 was created to address issues identified, however it doesn't
> seem to have been solved properly.
>
> - The changes to the NOTICE file don't match the NOTICE file for Guice.
> There is no need to declare the license usage for single licensed code.
> - You added the LGPL license.  You cannot include LGPL binaries.  However,
> I can't find the binaries so it should probably just be omitted.
>
> Other things look fine.
>
> John
>
> On Mon, Sep 18, 2017 at 1:13 PM Andreas Neumann  wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.13.0-incubating,
> > release candidate 2. This is the sixth release of Tephra.
> >
> > The Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> > http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201709.mbox/%
> > 3CCANpmDOfN7MPHYjKt-PqNd3yY1KtgyNn6L1ANT63xxPEdSsXQuA%40mail.gmail.com
> %3E
> >  dev/201709.mbox/%3CCANpmDOfN7MPHYjKt-PqNd3yY1KtgyNn6L1ANT63xxPEdSsX
> QuA%40mail.gmail.com%3E>
> >
> > Result thread:
> > http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201709.mbox/%
> > 3CCANpmDOe8T70zU4h%2BgknSJ%2B%3DTOAkUw9praf46GTtuz-5Cr2-7jA%
> > 40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
> > .0-incubating-rc2/src
> >
> > The tag to be voted upon is v0.13.0-incubating:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > it;a=shortlog;h=refs/tags/v0.13.0-incubating
> >
> > The release hash is 37467ce63934aca86f84eb61493733bb470450d7:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > it;a=commit;h=37467ce63934aca86f84eb61493733bb470450d7
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1010
> >
> > Release artifacts are signed with the following key:
> > http://people.apache.org/keys/committer/anew
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
> > .0-incubating-rc2/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.13.0-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.13.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Andreas
> >
>

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[Alan Gates]

Forwarding my +1 from the dev list. 

Alan. 

Sent from my iPhone

> On Sep 19, 2017, at 03:56, James Taylor  wrote:
> 
> +1. Transferring my vote over from the dev list vote.
> 
>> On Mon, Sep 18, 2017 at 10:13 AM, Andreas Neumann  wrote:
>> 
>> Hi all,
>> 
>> This is a call for a vote on releasing Apache Tephra 0.13.0-incubating,
>> release candidate 2. This is the sixth release of Tephra.
>> 
>> The Apache Tephra community has voted and approved the release.
>> 
>> Vote thread:
>> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
>> dev/201709.mbox/%
>> 3CCANpmDOfN7MPHYjKt-PqNd3yY1KtgyNn6L1ANT63xxPEdSsXQuA%40mail.gmail.com%3E
>> 
>> Result thread:
>> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
>> dev/201709.mbox/%
>> 3CCANpmDOe8T70zU4h%2BgknSJ%2B%3DTOAkUw9praf46GTtuz-5Cr2-7jA%
>> 40mail.gmail.com%3E
>> 
>> The source tarball, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
>> .0-incubating-rc2/src
>> 
>> The tag to be voted upon is v0.13.0-incubating:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> it;a=shortlog;h=refs/tags/v0.13.0-incubating
>> 
>> The release hash is 37467ce63934aca86f84eb61493733bb470450d7:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> it;a=commit;h=37467ce63934aca86f84eb61493733bb470450d7
>> 
>> The Nexus Staging URL:
>> https://repository.apache.org/content/repositories/orgapachetephra-1010
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/anew
>> 
>> KEYS file available:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>> 
>> For information about the contents of this release, see:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
>> .0-incubating-rc2/CHANGES.txt
>> 
>> Please vote on releasing this package as Apache Tephra 0.13.0-incubating
>> 
>> The vote will be open for 72 hours.
>> 
>> [ ] +1 Release this package as Apache Tephra 0.13.0-incubating
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Thanks,
>> Andreas
>> 

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

Re: [VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

On Sat, Jul 1, 2017 at 8:37 AM, Ruilong Huo  wrote:

> Hi IPMC member,
>
>
> The PPMC vote for the Apache HAWQ 2.2.0.0-incubating release has passed.
> We kindly request that the IPMC now vote on the release.
>
>
> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/ee0b81127e75eb2562e91b0a44d56b
> 24165c6284a7a46dc03eeb7d6d@%3Cdev.hawq.apache.org%3E
>
>
> The artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.
> 0-incubating.RC3/
>
>
> The artifacts have been signed with Key : 1B8B6872
>
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 2.2.0.0-incubating'. You can view them here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318826=12339641
>
>
> Please vote accordingly:
> [ ] +1, accept as the official Apache HAWQ 2.2.0.0-incubating release
> [ ] -1, do not accept as the official Apache HAWQ 2.2.0.0-incubating
> release because...
>
>
> The vote will run for at least 72 hours.
>
>
> Best regards,
> Ruilong Huo

Re: [NOTICE] Community Vote for Apache Atlas Graduation to TLP

[Alan Gates]

https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118

Alan.

On Mon, Jun 5, 2017 at 6:26 PM, John D. Ament 
wrote:

> Suma,
>
> One more thing.  I cannot find a podling name search on file for Atlas.
> Has this been done?  See also [1]
>
> John
>
> [1]: http://incubator.apache.org/guides/names.html#name-search
>
> On Thu, May 25, 2017 at 8:45 PM John D. Ament 
> wrote:
>
> > Hi Suma,
> >
> > Thanks for the heads up.  There is actually no requirement for the
> podling
> > community to vote on graduation, but its a good sign.
> >
> > I'm a little concerned, can you double check your status file at [1] ?
> > Most of the items are marked N/A which is weird, most of these should
> > actually have dates.
> >
> > In addition, can you provide a list of committers you have added since
> > starting at Apache?  The podling status report shows none, but it may be
> > that your status file is not up to date.
> >
> > [1]: http://incubator.apache.org/projects/atlas.html
> >
> >
> > On Thu, May 25, 2017 at 8:33 PM Suma Shivaprasad 
> > wrote:
> >
> >> Dear Incubator members,
> >>
> >> Please note that the community vote for graduating Apache Atlas to TLP
> has
> >> commenced and has so far received a very positive response from the
> Atlas
> >> community. You can find the vote thread at https://s.apache.org/94xI.
> >>
> >> Thanks
> >> Suma
> >>
> >
>

Re: [VOTE] Release of Apache Tephra-0.12.0-incubating [rc1]

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

On Fri, May 26, 2017 at 2:12 PM, Gokul Gunasekaran  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.12.0-incubating,
> release candidate 1. This is the fifth release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201705.mbox/%
> 3CCAFgkoWGFt1m4puB-T83i0QCgbyqpR7SEiMqJHL8b%3DxVCcSmvng%40mail.gmail.com%
> 3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201705.mbox/%3CCAFgkoWG5%3Dz9Fuu2xzLTiEOgFmTmZs53VRij7a
> k3Zu2YY%2B2kciw%40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.12
> .0-incubating-rc1/src
>
> The tag to be voted upon is v0.12.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=shortlog;h=refs/tags/v0.12.0-incubating
>
> The release hash is 2bc62de4498bdb1d6b4647d6f102649d3f9d5df7:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=commit;h=2bc62de4498bdb1d6b4647d6f102649d3f9d5df7
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1008/
>
> Release artifacts are signed by:
> http://people.apache.org/keys/committer/gokul
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> *https://dist.apache.org/repos/dist/dev/incubator/
> tephra/0.12.0-incubating-rc1/CHANGES.txt
>  tephra/0.12.0-incubating-rc1/CHANGES.txt>*
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.12.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Gokul
>

Re: [VOTE] Release Apache Atlas 0.8 (incubating) RC1

[Alan Gates]

+1.  Checked the signatures, LICENSE, NOTICE, and DISCLAIMER files, did a build 
with a clean repo, and ran rat.

Alan.

> On Mar 11, 2017, at 9:46 AM, Madhan Neethiraj  wrote:
> 
> Incubator PMC,
> 
> Apache Atlas community has voted on and approved the proposal to release 
> Apache Atlas 0.8 (incubating).
>  - vote result thread: 
> https://lists.apache.org/thread.html/f4bdc475b0de0278c51f7875838ab9b4ac3b83a70855007ca967891e@%3Cdev.atlas.apache.org%3E
>  - vote thread: 
> https://lists.apache.org/thread.html/c030c13ee931852f9d3e52647958e1e0cf740b5bdedca74500f119b2@%3Cdev.atlas.apache.org%3E
> 
> Apache Atlas 0.8 (incubating) release candidate #1 is now available for IPMC 
> vote. Please review and vote.
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Thanks,
> Madhan
> 
> 
> List of improvements and issues addressed in this release: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8-incubating%20ORDER%20BY%20key%20DESC
> 
> Git tag for the release: 
> https://github.com/apache/incubator-atlas/tree/release-0.8-rc1
> 
> Sources for the release: 
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz
> 
> Source release verification:
>  PGP Signature:  
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz.asc
>  MD5 Hash:   
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz.md5
> 
> Keys to verify the signature of the release artifacts are available at: 
> https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Release of Apache Tephra-0.11.0-incubating [rc2]

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Mar 10, 2017, at 5:18 PM, Gokul Gunasekaran  wrote:
> 
> Hi all,
> 
> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> release candidate 2. This is the fourth release of Tephra.
> 
> Apache Tephra community has voted and approved the release.
> 
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201703.mbox/%3CCAFgkoWEhJrFB5WdUJBh3qe5v9UqYxPHLRQRJQBKUr7gD%2BHOCEA%40mail.gmail.com%3E
> 
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201703.mbox/%3CCAFgkoWHo6bQ6sN_X64_%3Df5PYV2SLhdswZ%2BbBbpp-jHK3smpALw%40mail.gmail.com%3E
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11.0-incubating-rc2/src
> 
> The tag to be voted upon is v0.11.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.11.0-incubating
> 
> The release hash is 6c0ba4da1597394d9d24bfde7f50a8793ac85e67:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=6c0ba4da1597394d9d24bfde7f50a8793ac85e67
> 
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1007/
> 
> Release artifacts are signed by:
> http://people.apache.org/keys/committer/gokul
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> 
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11.0-incubating-rc2/CHANGES.txt
> 
> Please vote on releasing this package as Apache Tephra 0.11.0-incubating.
> Note that the vote for rc1 was canceled due to the bug
> https://issues.apache.org/jira/browse/TEPHRA-223. This bug is fixed in rc2.
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Gokul


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

Re: [VOTE] Release Apache HAWQ 2.1.0.0-incubating (RC4)

[Alan Gates]

Forwarding my +1 from the PPMC vote.

Alan.

> On Feb 21, 2017, at 5:54 PM, Ed Espino  wrote:
> 
> Hello Incubator PMC (IPMC),
> 
> The Apache HAWQ community has voted on and approved a proposal to
> release Apache HAWQ 2.1.0.0-incubating (source only release).
> 
> We kindly request that the IPMC members review and vote on this
> incubator release.
> 
> The PPMC VOTE thread is here:
> https://lists.apache.org/thread.html/b641ddf4519feba01d3d4c55180be842a27e75bdaef640175b623e12@%3Cdev.hawq.apache.org%3E
> 
> The PPMC VOTE RESULT is here:
> https://lists.apache.org/thread.html/9d3025c12dc032437d1317d662f0e4434754c00258ca1abdd5c0ab9f@%3Cdev.hawq.apache.org%3E
> 
> All JIRAs completed for this release are tagged with:
>  fixVersion = 2.1.0.0-incubating
> 
> A complete JIRA list can be reviewed here:
> *
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318826=12339640
> 
> The tag to be voted on: 2.1.0.0-incubating-rc4
> (f5033eaa3c7c1d9f85bbcc56e9d921d96337831a), located here:
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=commit;h=12c7df017551f1c3b0deb38c7243db3e018ef62c
> 
> Git release branch:
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=shortlog;h=refs/heads/2.1.0.0-incubating
> 
> Source release package:
> *
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC4/apache-hawq-src-2.1.0.0-incubating.tar.gz
> 
> Source release verification:
> * PGP Signature:
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC4/apache-hawq-src-2.1.0.0-incubating.tar.gz.asc
> * SHA256/MD5 Hash:
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC4/apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC4/apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
> 
> Keys to verify the signature of the release artifact are available at:
> * https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
> 
> The artifact(s) has been signed with Key ID: 57325522 ("esp...@apache.org")
> 
> Build instructions are included in the project's wiki:
> https://cwiki.apache.org/confluence/display/HAWQ/Build+and+Install
> 
> When voting, please list the actions taken to verify the release. To
> facilitate Apache license review and conformance, an Apache Release
> Audit Tool (RAT) pom.xml file is included in the source root
> directory.
> 
> The vote will be open for at least 72 hours.
> 
> Please vote:
> [ ] +1 Approve the release
> [ ] +0 no opinion
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> Thanks,
> -=ed espino
> 
> -- 
> *Ed Espino*
> *esp...@apache.org *


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

Re: [VOTE] Release of Apache Tephra-0.11.0-incubating [rc1]

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Feb 17, 2017, at 11:52 AM, James Taylor  wrote:
> 
> Transferring my +1 from the dev list vote over here.
> 
> On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran 
> wrote:
> 
>> Hi all,
>> 
>> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
>> release candidate 1. This is the fourth release of Tephra.
>> 
>> Apache Tephra community has voted and approved the release.
>> 
>> Vote thread:
>> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
>> dev/201702.mbox/%
>> 3CCAFgkoWEmagPPMPLREsK2CvWmS97_g0AE_1Bd7P1UWXbc3wYv-g%40mail.gmail.com%3E
>> 
>> Result thread:
>> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
>> dev/201702.mbox/%3CCAFgkoWE4T5PoieC4aPQWK040i5L
>> VHwbvnZ%2BH%3DnqwGu_O96Yf9A%40mail.gmail.com%3E
>> 
>> 
>> The source tarball, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
>> .0-incubating-rc1/src
>> 
>> The tag to be voted upon is v0.11.0-incubating:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> it;a=shortlog;h=refs/tags/v0.11.0-incubating
>> 
>> The release hash is d6327007b6240c9b2605c2e8d91ca9ac92ecedfc:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> it;a=commit;h=d6327007b6240c9b2605c2e8d91ca9ac92ecedfc
>> 
>> The Nexus Staging URL:
>> https://repository.apache.org/content/repositories/orgapachetephra-1006
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/gokul
>> 
>> KEYS file available:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>> 
>> For information about the contents of this release, see:
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
>> .0-incubating-rc1/CHANGES.txt
>> 
>> Please vote on releasing this package as Apache Tephra 0.11.0-incubating
>> 
>> The vote will be open for 72 hours.
>> 
>> [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Thanks,
>> Gokul
>> 


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

Re: [VOTE] Release Apache HAWQ 2.1.0.0-incubating (RC3)

[Alan Gates]

Generally we don't want binary files in source releases, so unless there's a 
very strong reason to continue with the release I'd say it's better to respin 
it.

Alan.

> On Feb 9, 2017, at 11:15 AM, Ed Espino <esp...@apache.org> wrote:
> 
> Alan,
> 
> Please, no need to apologize.  We appreciate your review contributions
> immensely.  I was just getting a bit anxious as this is my initial time
> being a release manager for an Apache project.
> 
> Does the existence of the jar files warrant another release candidate or
> can we fix HAWQ-1319 in the next release?
> 
> -=e
> 
> On Thu, Feb 9, 2017 at 11:00 AM, Alan Gates <alanfga...@gmail.com> wrote:
> 
>> I responded on the thread.  Sorry, I should have seen this sooner and
>> voted on it.
>> 
>> Alan.
>> 
>>> On Feb 9, 2017, at 10:48 AM, Ed Espino <esp...@apache.org> wrote:
>>> 
>>> Good catch Alan. I agree with you that the jar files should be removed. I
>>> have created https://issues.apache.org/jira/browse/HAWQ-1319 to address
>>> this issue.
>>> 
>>> Regards,
>>> -=e
>>> 
>>> On Thu, Feb 9, 2017 at 10:25 AM, Alan Gates <alanfga...@gmail.com>
>> wrote:
>>> 
>>>> I checked the licenses, notice, disclaimer, and signatures.  These all
>>>> look good.
>>>> 
>>>> One question, there are a couple of jar files in a test directory,
>>>> ./src/test/feature/UDF/sql/PLJavaAdd.jar and
>> ./src/test/feature/UDF/sql/
>>>> PLJavauAdd.jar
>>>> In general it's a bad idea to include binary files since users have a
>> hard
>>>> time verifying their contents.  Are these necessary?  Could they not be
>>>> built as part of the build?
>>>> 
>>>> Alan.
>>>> 
>>>>> On Feb 7, 2017, at 11:33 PM, Ed Espino <esp...@apache.org> wrote:
>>>>> 
>>>>> Hello Incubator PMC (IPMC),
>>>>> 
>>>>> The Apache HAWQ community has voted on and approved a proposal to
>>>>> release Apache HAWQ 2.1.0.0-incubating (source only release).
>>>>> 
>>>>> We kindly request that the IPMC members review and vote on this
>>>>> incubator release.
>>>>> 
>>>>> The PPMC VOTE thread is here:
>>>>> https://lists.apache.org/thread.html/ac664618426411fa2021b2b36b4ce4
>>>> 2f9d5bc505a9aa8d901c14fbbd@%3Cdev.hawq.apache.org%3E
>>>>> 
>>>>> The PPMC VOTE RESULT is here:
>>>>> https://lists.apache.org/thread.html/4463b3f7bee2d7e3e10e71fe01ce70
>>>> 348bd23a493e00d08730343eea@%3Cdev.hawq.apache.org%3E
>>>>> 
>>>>> All JIRAs completed for this release are tagged with:
>>>>> fixVersion = 2.1.0.0-incubating
>>>>> A complete JIRA list can be reviewed here:
>>>>> *
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>>> projectId=12318826=12338900
>>>>> 
>>>>> The tag to be voted on: 2.1.0.0-incubating-rc3
>>>>> *
>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.
>> git;a=commit;h=
>>>> 12c7df017551f1c3b0deb38c7243db3e018ef62c
>>>>> 
>>>>> Git release branch:
>>>>> *
>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.
>>>> git;a=shortlog;h=refs/heads/2.1.0.0-incubating
>>>>> 
>>>>> Source release package:
>>>>> *
>>>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>>>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz
>>>>> 
>>>>> Source release verification:
>>>>> * PGP Signature:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>>>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.asc
>>>>> * SHA256/MD5 Hash:
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>>>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256
>>>>> 
>>>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>>>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
>>>>> 
>>>>> Keys to verify the signature of the release artifact are available at:
>>>>> * https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
>>>>> 
>>>>> T

Re: [VOTE] Release Apache HAWQ 2.1.0.0-incubating (RC3)

[Alan Gates]

I responded on the thread.  Sorry, I should have seen this sooner and voted on 
it.

Alan.

> On Feb 9, 2017, at 10:48 AM, Ed Espino <esp...@apache.org> wrote:
> 
> Good catch Alan. I agree with you that the jar files should be removed. I
> have created https://issues.apache.org/jira/browse/HAWQ-1319 to address
> this issue.
> 
> Regards,
> -=e
> 
> On Thu, Feb 9, 2017 at 10:25 AM, Alan Gates <alanfga...@gmail.com> wrote:
> 
>> I checked the licenses, notice, disclaimer, and signatures.  These all
>> look good.
>> 
>> One question, there are a couple of jar files in a test directory,
>> ./src/test/feature/UDF/sql/PLJavaAdd.jar and ./src/test/feature/UDF/sql/
>> PLJavauAdd.jar
>> In general it's a bad idea to include binary files since users have a hard
>> time verifying their contents.  Are these necessary?  Could they not be
>> built as part of the build?
>> 
>> Alan.
>> 
>>> On Feb 7, 2017, at 11:33 PM, Ed Espino <esp...@apache.org> wrote:
>>> 
>>> Hello Incubator PMC (IPMC),
>>> 
>>> The Apache HAWQ community has voted on and approved a proposal to
>>> release Apache HAWQ 2.1.0.0-incubating (source only release).
>>> 
>>> We kindly request that the IPMC members review and vote on this
>>> incubator release.
>>> 
>>> The PPMC VOTE thread is here:
>>> https://lists.apache.org/thread.html/ac664618426411fa2021b2b36b4ce4
>> 2f9d5bc505a9aa8d901c14fbbd@%3Cdev.hawq.apache.org%3E
>>> 
>>> The PPMC VOTE RESULT is here:
>>> https://lists.apache.org/thread.html/4463b3f7bee2d7e3e10e71fe01ce70
>> 348bd23a493e00d08730343eea@%3Cdev.hawq.apache.org%3E
>>> 
>>> All JIRAs completed for this release are tagged with:
>>> fixVersion = 2.1.0.0-incubating
>>> A complete JIRA list can be reviewed here:
>>> *
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12318826=12338900
>>> 
>>> The tag to be voted on: 2.1.0.0-incubating-rc3
>>> *
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=commit;h=
>> 12c7df017551f1c3b0deb38c7243db3e018ef62c
>>> 
>>> Git release branch:
>>> *
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.
>> git;a=shortlog;h=refs/heads/2.1.0.0-incubating
>>> 
>>> Source release package:
>>> *
>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz
>>> 
>>> Source release verification:
>>> * PGP Signature:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.asc
>>> * SHA256/MD5 Hash:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.
>> 0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
>>> 
>>> Keys to verify the signature of the release artifact are available at:
>>> * https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
>>> 
>>> The artifact(s) has been signed with Key ID: 57325522 ("
>> esp...@apache.org")
>>> 
>>> Build instructions are included in the project's wiki:
>>> https://cwiki.apache.org/confluence/display/HAWQ/Build+and+Install
>>> 
>>> When voting, please list the actions taken to verify the release. To
>>> facilitate Apache license review and conformance, an Apache Release
>>> Audit Tool (RAT) pom.xml file is included in the source root
>>> directory.
>>> 
>>> The vote will be open for at least 72 hours.
>>> 
>>> Please vote:
>>> [ ] +1 Approve the release
>>> [ ] +0 no opinion
>>> [ ] -1 Don't approve the release (please provide specific comments)
>>> 
>>> Thanks,
>>> -=ed espino
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> 
> -- 
> *Ed Espino*
> *esp...@apache.org <esp...@apache.org>*


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

Re: [VOTE] Release Apache HAWQ 2.1.0.0-incubating (RC3)

[Alan Gates]

I checked the licenses, notice, disclaimer, and signatures.  These all look 
good.  

One question, there are a couple of jar files in a test directory, 
./src/test/feature/UDF/sql/PLJavaAdd.jar and 
./src/test/feature/UDF/sql/PLJavauAdd.jar
In general it's a bad idea to include binary files since users have a hard time 
verifying their contents.  Are these necessary?  Could they not be built as 
part of the build?

Alan.

> On Feb 7, 2017, at 11:33 PM, Ed Espino  wrote:
> 
> Hello Incubator PMC (IPMC),
> 
> The Apache HAWQ community has voted on and approved a proposal to
> release Apache HAWQ 2.1.0.0-incubating (source only release).
> 
> We kindly request that the IPMC members review and vote on this
> incubator release.
> 
> The PPMC VOTE thread is here:
> https://lists.apache.org/thread.html/ac664618426411fa2021b2b36b4ce42f9d5bc505a9aa8d901c14fbbd@%3Cdev.hawq.apache.org%3E
> 
> The PPMC VOTE RESULT is here:
> https://lists.apache.org/thread.html/4463b3f7bee2d7e3e10e71fe01ce70348bd23a493e00d08730343eea@%3Cdev.hawq.apache.org%3E
> 
> All JIRAs completed for this release are tagged with:
>  fixVersion = 2.1.0.0-incubating
> A complete JIRA list can be reviewed here:
> *
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318826=12338900
> 
> The tag to be voted on: 2.1.0.0-incubating-rc3
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=commit;h=12c7df017551f1c3b0deb38c7243db3e018ef62c
> 
> Git release branch:
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=shortlog;h=refs/heads/2.1.0.0-incubating
> 
> Source release package:
> *
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz
> 
> Source release verification:
> * PGP Signature:
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.asc
> * SHA256/MD5 Hash:
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256
> 
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.1.0.0-incubating.RC3/apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
> 
> Keys to verify the signature of the release artifact are available at:
> * https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
> 
> The artifact(s) has been signed with Key ID: 57325522 ("esp...@apache.org")
> 
> Build instructions are included in the project's wiki:
> https://cwiki.apache.org/confluence/display/HAWQ/Build+and+Install
> 
> When voting, please list the actions taken to verify the release. To
> facilitate Apache license review and conformance, an Apache Release
> Audit Tool (RAT) pom.xml file is included in the source root
> directory.
> 
> The vote will be open for at least 72 hours.
> 
> Please vote:
> [ ] +1 Approve the release
> [ ] +0 no opinion
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> Thanks,
> -=ed espino


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

Re: [VOTE] Release Apache Ranger 0.6.2 (incubating) - rc1

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Nov 1, 2016, at 20:00, Velmurugan Periasamy  wrote:
> 
> Incubator PMC:
> 
> Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.6.2 (incubating). 
> 
> [VOTE RESULT] thread:
>
> https://lists.apache.org/thread.html/11302204c77df6c9d86a3e75078ba0a9690a09bf186c5277acdce11b@%3Cdev.ranger.apache.org%3E
> 
> Apache ranger-0.6.2-rc1 release candidate is now available with the following 
> artifacts up for IPMC vote. I kindly request that the Incubator PMC members 
> review and vote on this incubator release.
> 
> Git tag for the release:
>https://github.com/apache/incubator-ranger/tree/ranger-0.6.2-rc1
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.2-incubating-rc1/apache-ranger-incubating-0.6.2.tar.gz
> Source release verification:
>PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.2-incubating-rc1/apache-ranger-incubating-0.6.2.tar.gz.asc
>MD5/SHA  Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.2-incubating-rc1/apache-ranger-incubating-0.6.2.tar.gz.mds
> Keys to verify the signature of the release artifact are available at:
>https://people.apache.org/keys/group/ranger.asc
> 
> Release Notes:
>
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.6.2+-+Release+Notes
> Build verification steps can be found at:
>http://ranger.incubator.apache.org/quick_start_guide.html
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding).
> 
> Thank you,
> Vel


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

Re: [VOTE] Apache HAWQ 2.0.0.0-incubating RC4

[Alan Gates]

+1.  Checked the signatures, DISCLAIMER, NOTICE, and many LICENSE files (wow, 
26, there must be an award for having that many).  Ran rat, which seemed happy.

Alan.

> On Sep 30, 2016, at 12:23, Goden Yao  wrote:
> 
> Hi IPMC,
> 
> HAWQ community has voted and passed RC4 build. Previous IP issues have all
> been fixed.
> The Vote thread can be found:
> http://mail-archives.apache.org/mod_mbox/incubator-hawq-dev/201609.mbox/%3CCABJ%3DBRr4xY_J0AY6Jfdvzd_uyOQAsEr9UrF6chOnRy2dEGMwmQ%40mail.gmail.com%3E
> 
> 
> This is the 1st release for Apache HAWQ (incubating), version:
> 2.0.0.0-incubating
> I want to take the opportunity to thank Ed, Roman and Justin for the final
> verification of all IP issues.
> 
> *It fixes the following issues:*
> Clear all IP related issues for HAWQ and this is a source code tarball only
> release.
> Full list of JIRAs fixed/related to the release: link
> 
> 
> *We're voting upon the release branch:*
> 2.0.0.0-incubating
> HEAD: commit
> 
> 
> To run check RAT, please do:
> 
> $mvn verify
> 
> first to get the correct RAT output.  Look inside of pom.xml to see the
> classes of exceptions we're managing there for RAT.
> 
> *Source Files:*
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.0.0.0-incubating.RC4
> 
> *KEYS file containing PGP Keys we use to sign the release:*
> https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
> (please note that I used new key to sign and my old key is going to be
> revoked)
> 
> This vote will be open for at least 72 hours, or until the necessary number
> of votes reached.
> 
> Thanks
> -Goden


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

Re: [DISCUSS] Olympian Incubation Proposal

[Alan Gates]

When we asked DataStax if they would sign a code grant, they were clear that 
they would not.  When we asked if they were opposed to us taking a fork to 
Apache, we got no response, despite trying on multiple channels.  I don’t know 
if this is enough to accept the podling or not, but it’s the best we’re going 
to get.

Alan.

> On Sep 29, 2016, at 01:20, Bertrand Delacretaz  wrote:
> 
> Hi,
> 
> On Thu, Sep 29, 2016 at 6:01 AM, Henry Saputra  
> wrote:
>> ...This project will be a fork of Titan graph database project...
>> ...The project was created by company called Aurelius and was acquired by
>> Datstax...
> 
> We only accept friendly forks, and it looks like Titan belongs to
> DataStax, so IMO you need at least an informal agreement from them
> before forking at the ASF.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Release SAMOA 0.4.0 (incubating) RC1

[Alan Gates]

+1.  Checked the LICENSE, NOTICE, and DISCLAIMER files.  Checked the 
signatures.  Did a build with a clean maven repo.  Checked for binary files.  
Ran a rat check.

As a note there are several files that rat complains about.  Based on a quick 
look I’m not sure it’s possible to add license headers to these files.  If it 
isn’t it would be nice to put these in the exception list so that rat succeeds.

Alan.

> On Sep 19, 2016, at 06:50, Nicolas Kourtellis  wrote:
> 
> Hi all,
> 
> Our new release has been voted from the Apache SAMOA team and we are
> opening the vote to the incubator email list for testing.
> 
> Please vote on releasing the following release candidate as Apache
> SAMOA (incubating)
> version 0.4.0. This release will be the second release for SAMOA in the
> incubator.
> 
> -
> The commit to be voted on is in the branch "releases/0.4.0-incubating"
> (commit fc39238dd7d3674c069a8142312da8c1812bc907):
> https://git1-us-west.apache.org/repos/asf/incubator-samoa/
> repo?p=incubator-samoa.git;a=commit;h=fc39238dd7d3674c069a8142312da8
> c1812bc907
> 
> Tag v0.4.0-incubating:
> https://git1-us-west.apache.org/repos/asf/incubator-samoa/
> repo?p=incubator-samoa.git;a=tag;h=aa5bd941ccbed1aabb46b8119049ac1bb293c3a2
> 
> Release artifacts are signed with the following key:
> *https://people.apache.org/keys/committer/nkourtellis.asc
> *
> 
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/staging/
> org/apache/samoa/samoa/0.4.0-incubating/
> 
> The developer's version artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/samoa/0.4.0-incubating-rc1/
> 
> -
> 
> Please vote on releasing this package as Apache SAMOA 0.4.0 (incubating).
> 
> The vote is open for the next 72 hours and passes if a majority of at least
> three +1 PPMC votes are cast.
> 
> [ ] +1 Release this package as Apache SAMOA 0.4.0 (incubating)
> [ ] -1 Do not release this package because ...
> 
> I'm +1 on the release.
> 
> Cheers,
> 
> Nicolas
> 
> 
> 
> -- 
> Nicolas Kourtellis


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

Re: [VOTE] Release of Apache Tephra-0.9.0-incubating [rc1]

[Alan Gates]

Forwarding my +1 from the vote on the dev list.

Alan.

> On Sep 15, 2016, at 22:44, Poorna Chandra  wrote:
> 
> Hi all,
> 
> This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
> release candidate 1. This is the second release of Tephra.
> 
> Apache Tephra community has voted and approved the release.
> 
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21R4KR-e%3DmzCsefvokpQWykOXTTnWt%2BZwt0CjiZz1MsqAg%40mail.gmail.com%3E
> 
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21Q9RJqDAo9n_AJWKaPm9_9iM4JoOL0bK9uh2thhS5Jn1g%40mail.gmail.com%3E
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/src
> 
> The tag to be voted upon is v0.9.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.9.0-incubating
> 
> The release hash is db235cdfa0d40d4e31bcd19ab350e9961719c79e:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=db235cdfa0d40d4e31bcd19ab350e9961719c79e
> 
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1004
> 
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/poorna
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> 
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/CHANGES.txt
> 
> Please vote on releasing this package as Apache Tephra 0.9.0-incubating
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 Release this package as Apache Tephra 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Poorna.


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

Re: [VOTE] Release apache-singa-incubating-1.0.0 (RC2)

[Alan Gates]

+1.  Checked signatures, DISCLAIMER, LICENSE, and NOTICE files, and assured 
there were no binary files in the distribution.

Alan.

> On Sep 3, 2016, at 02:33, WANG Sheng  wrote:
> 
> Hi all,
> 
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 1.0.0 (incubating).
> 
> The vote thread is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201609.mbox/%3CCAELsgRf0T371qTSVo20HjTGiXYgW-br7YgnffUHgAxTooqW9qQ%40mail.gmail.com%3E
> 
> and the result is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201609.mbox/%3CCAELsgRcyMcB%3DF5XgtOv1P9zuNPbU7-qWmnCNbDpRrJu4ReP9ug%40mail.gmail.com%3E
> 
> We ask the IPMC to vote on this release.
> 
> The artifacts to be voted on are located at:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.0.0/
> 
> The hashes of the artifacts are as follows:
> MD5: AE 01 1F 67 D7 F0 F6 23  FF 26 F9 A9 F0 00 1C C3
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dinhtta.asc
> 
> and the signature file is:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.0.0/apache-singa-incubating-1.0.0-RC2.tar.gz.asc
> 
> The Github tag is at:
> https://github.com/apache/incubator-singa/releases/tag/v1.0.0-rc2
> 
> with commit ID: 0416a0fdfa63cb1b4f54e438ff5b33d7eb4d8df0
> 
> To check the license, you can use the Apache Rat tool as follows:
> 1. download & decompress apache rat from
> http://creadur.apache.org/rat/download_rat.cgi
> 2. run the following command under singa folder:
>java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> rat_check
> 3. check the results in file named "rat_check"
> 
> The vote is open for at least 72 hours, or until the necessary number of
> votes (3 +1) is reached.
> 
> [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> Regards,
> Sheng


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

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Aug 16, 2016, at 15:05, Selvamohan Neethiraj  wrote:
> 
> Incubator PMC:
> 
> Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.6.1 (incubating). 
> [VOTE RESULT] thread from dev community:
> - 
> https://lists.apache.org/thread.html/53bc84b26d76bb76a1c4375172fb43c5335865d82d4eead3ad374993@%3Cdev.ranger.apache.org%3E
> - 
> https://lists.apache.org/thread.html/02daa7ebce5588e170eb6fdf747a6df52dadc1dfe8aee4dcd6260d2b@%3Cdev.ranger.apache.org%3E
> 
> 
> Apache ranger-0.6.1-rc2 release candidate is now available with the following 
> artifacts up for IPMC vote. 
> I kindly request that the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Release (Source) Information:
> Git tag for the release:
>  https://github.com/apache/incubator-ranger/commits/ranger-0.6.1-rc2 (last 
> commit id :  428f1207e694e9d2648ddaeddd2b0cea79d765ea)
> Sources for the release:
>   
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz
> 
> Source release verification:
> PGP Signature:  
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz.asc
> MD5/SHA  Hash:
>   
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz.mds
> Keys to verify the signature of the release artifact are available at:
>   https://people.apache.org/keys/group/ranger.asc
> Build verification steps can be found at:
>http://ranger.incubator.apache.org/quick_start_guide.html
> 
> 
> Release Notes:
>
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.6.1+-+Release+Notes
> 
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding).
> 
> Thank you,
> Selva-
> 
> 


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

Re: [VOTE] Apache HAWQ (incubating) 2.0.0.0-incubating Release

[Alan Gates]

My mistake on the binaries.  I did a ‘find . -type f -exec file {} \;’ and it 
turned up a bunch of files that it said were unstripped executables, but I 
didn’t notice that they were in a directory called ‘hawq-data’, so I assume 
these are test data files, not actual executables.  Sorry about that.

Alan.

> On Jul 26, 2016, at 14:51, Ting(Goden) Yao <t...@pivotal.io> wrote:
> 
> Thanks Alan for the prompt feedback.
> I filed: https://issues.apache.org/jira/browse/HAWQ-952 for the COPYRIGHT
> file issue.
> 
> For executable binary files in , can you be more specific?  I
> couldn't locate them in source tree and hopefully I didn't pack them by
> mistake.
> 
> On Tue, Jul 26, 2016 at 2:32 PM Alan Gates <alanfga...@gmail.com> wrote:
> 
>> -1.  There are a number of binary executables in the contrib directory.
>> Binary executables can’t be in a source release.
>> 
>> Also, the contents of the COPYRIGHT file should be in NOTICE rather than
>> in a separate file.
>> 
>> Alan.
>> 
>> 
>>> On Jul 26, 2016, at 10:31, Goden Yao <goden...@apache.org> wrote:
>>> 
>>> Hi IPMC,
>>> 
>>> The PPMC vote to release Apache HAWQ 2.0.0.0-incubating has passed.
>>> We've got eleven +1 Votes zero -1 or 0 votes from the community.
>>> 
>>> The PPMC vote thread is here:
>>> 
>> https://lists.apache.org/thread.html/c285399e2aa3f4d3cc085654779f45bebccf2124df40bf2ec355c183@%3Cdev.hawq.apache.org%3E
>>> 
>>> 
>>> *This release fixes the following issues:*
>>> Clear all IP related issues for HAWQ and this is a source code tarball
>> only
>>> release.
>>> Full list of JIRAs fixed/related to the release: link
>>> <
>> https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.0.0.0-incubating
>>> 
>>> 
>>> *We're voting upon the release branch:*
>>> 2.0.0.0-incubating
>>> HEAD: commit
>>> <
>> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq.git;a=commit;h=9bdad43ebbbcefce23db193c3a7dd62ea6a3d805
>>> 
>>> 
>>> 
>>> *Source Files:*
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.0.0.0-incubating.RC2
>>> 
>>> *KEYS file containing PGP Keys we use to sign the release:*
>>> https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
>>> 
>>>  Please download and evaluate the release candidate build *** *(in
>> IP,
>>> license, RAT check, etc.)
>>> The vote will be open for at least 72 hours or until necessary number of
>>> votes
>>> 
>>> Please vote:
>>> [ ] +1 Release this tarball
>>> [ ] +0 no opinion
>>> [ ] -1 Do not release as ...
>>> 
>>> Thanks
>>> -Goden
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: [VOTE] Apache HAWQ (incubating) 2.0.0.0-incubating Release

[Alan Gates]

-1.  There are a number of binary executables in the contrib directory.  Binary 
executables can’t be in a source release.

Also, the contents of the COPYRIGHT file should be in NOTICE rather than in a 
separate file.

Alan.


> On Jul 26, 2016, at 10:31, Goden Yao  wrote:
> 
> Hi IPMC,
> 
> The PPMC vote to release Apache HAWQ 2.0.0.0-incubating has passed.
> We've got eleven +1 Votes zero -1 or 0 votes from the community.
> 
> The PPMC vote thread is here:
> https://lists.apache.org/thread.html/c285399e2aa3f4d3cc085654779f45bebccf2124df40bf2ec355c183@%3Cdev.hawq.apache.org%3E
> 
> 
> *This release fixes the following issues:*
> Clear all IP related issues for HAWQ and this is a source code tarball only
> release.
> Full list of JIRAs fixed/related to the release: link
> 
> 
> *We're voting upon the release branch:*
> 2.0.0.0-incubating
> HEAD: commit
> 
> 
> 
> *Source Files:*
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.0.0.0-incubating.RC2
> 
> *KEYS file containing PGP Keys we use to sign the release:*
> https://dist.apache.org/repos/dist/dev/incubator/hawq/KEYS
> 
>  Please download and evaluate the release candidate build *** *(in IP,
> license, RAT check, etc.)
> The vote will be open for at least 72 hours or until necessary number of
> votes
> 
> Please vote:
> [ ] +1 Release this tarball
> [ ] +0 no opinion
> [ ] -1 Do not release as ...
> 
> Thanks
> -Goden


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

Re: [VOTE] Release Apache Ranger 0.6.0 (incubating) - rc1

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Jul 14, 2016, at 22:05, Velmurugan Periasamy  wrote:
> 
> Incubator PMC:
> 
> Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.6.0 (incubating). 
> 
> [VOTE RESULT] thread:
>
> https://lists.apache.org/thread.html/c21a99659362bcd2fef0119d9937b9ab245c99400902cf75a7e77910@%3Cdev.ranger.apache.org%3E
> 
> Apache ranger-0.6.0-rc1 release candidate is now available with the following 
> artifacts up for IPMC vote. I kindly request that the Incubator PMC members 
> review and vote on this incubator release.
> 
> Git tag for the release:
>https://github.com/apache/incubator-ranger/tree/ranger-0.6.0-rc1
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz
> Source release verification:
>PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz.asc
>MD5/SHA  Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz.mds
> Keys to verify the signature of the release artifact are available at:
>https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
> 
> Release Notes:
>https://cwiki.apache.org/confluence/display/RANGER/0.6.0+Release+Notes
> Build verification steps can be found at:
>http://ranger.incubator.apache.org/quick_start_guide.html
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding).
> 
> Thank you,
> Vel


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

Re: [VOTE] Release Apache Atlas version 0.7-incubating RC2

[Alan Gates]

+1.

I checked the LICENSE, DISCLAIMER, and NOTICE files.  Checked that there were 
no binary files in the distribution (there are images, but that seems ok).  
Checked the signatures.  Did a build with a fresh local maven repo with 
-DskipTests set.

When I built with tests it failed with:
Running org.apache.atlas.TestUtils
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.171 sec - in 
org.apache.atlas.TestUtils

Results :

Failed tests:
  StoreBackedTypeCacheTest.testGetTraitType:146 expected: but was:
  StoreBackedTypeCacheTest.testHasTraitType:164 expected: but was:

Tests run: 452, Failures: 2, Errors: 0, Skipped: 0

This isn’t enough to scuttle the release, though it’s nice when tests pass.  
I’m building on a Mac with JDK 1.8.

Alan.

> On Jul 6, 2016, at 00:09, Hemanth Yamijala  wrote:
> 
> Hi all,
> 
> This is a call for a vote on the Apache Atlas 0.7-incubating release
> (release candidate RC2).
> 
> A vote was held on developer mailing list and it passed with 7 +1s.
> 
> Vote thread: https://s.apache.org/Czm4
> Results thread: https://s.apache.org/PAeO
> 
> The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha512):
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc2/
> 
> The SHA512 checksum of the archive is
> 8B923CEA 2CDD32C8 7CE9A066 38002BFA 14F666DC C56F95AF 2805D5C1 08B58F9E 
> 436E3E3C
> 61B40908 474C67E7 782E720E 1BFA3678 B8099EBC 282F64C2 C16A48C4
> 
> The commit id (15748e7bc5ed019a63326f201258e3a55d512d96) to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=15748e7bc5ed019a63326f201258e3a55d512d96
> 
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs/tags/release-0.7-rc2
> 
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;hb=refs/heads/0.7-incubating
> 
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/atlas/KEYS
> PGP release keys:
> http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD
> 
> Note that this is a source only release and we are voting on the
> source release-0.7-incubating-rc2.
> 
> Please download, test, and try it out.
> 
> Vote will be open for at least 72 hours till 9th July, 2016 1 AM Pacific time.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Thank you!
> 
> Regards,
> Hemanth
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Release Apache Ranger 0.5.3 (incubating)

[Alan Gates]

-1 for now.  Justin has brought up some issues with the LICENSE and NOTICE 
files that have note been addressed.  Specifically:


- LICENSE is still missing a few things (same issues as previous release)
- NOTICE year is wrong and contains far too much text. There is not need to 
mention any permissive MIT licenses here.


The copyright year was fixed in the NOTICE file. LICENSE has not been changed 
and the MIT license has not been removed from NOTICE.

You should either make these changes or make an argument for why they are not 
necessary.  “We’ll do them next time” is not a good answer as that was said in 
the 0.5.2 release.

Alan.

> On May 7, 2016, at 08:09, Velmurugan Periasamy  wrote:
> 
> Incubator PMC:
> 
> The Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.5.3 (incubating) after addressing comments raised in IPMC 
> review for ranger-0.5.3-rc1 vote.
> 
> The ranger-0.5.3-rc2 release candidate is now available with the following 
> artifacts up for a project vote :
> 
> Git tag for the release:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=log;h=refs/tags/ranger-0.5.3-rc2
> 
> Source release:
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz
> 
> Source release verification:
> PGP signature: 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz.asc
> MD5/SHA Hash: 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz.mds
> Keys to verify the signature of the release artifact are available at: 
> https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
> 
> Release Notes:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62694969
> 
> Build verification steps can be found at: 
> http://ranger.incubator.apache.org/quick_start_guide.html
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding)
> 
> Thanks,
> Vel
> 


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

Re: [VOTE] Apache Apex Core Release 3.2.1-incubating (RC1)

[Alan Gates]

+1, checked LICENSE, NOTICE, and DISCLAIMER files.  Checked that no binaries 
are present.  Checked the signatures.

Alan.

> On Apr 17, 2016, at 15:01, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 binding - carried over form dev list all of the usual checks done.
> 
> Thanks,
> Justin
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Release apache-singa-incubating-0.3.0 (RC3)

[Alan Gates]

+1.  LICENSE, NOTICE, DISCLAIMER and rat check look good.  The signatures look 
good as well.  I didn’t find any binary files in the distribution.

Alan.

> On Apr 17, 2016, at 20:55, Anh Dinh  wrote:
> 
> Hi all,
> 
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 0.3.0 (incubating).
> 
> This release candidate (RC3) addressed the issue with the previous release
> candidate which contains Creative Common licensed file:
> https://issues.apache.org/jira/browse/SINGA-159
> 
> 
> The vote thread is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAAbkU4QROZh4qh1qorR0XMNGvwg5sMad-9JqggByO6vUVnxmtQ%40mail.gmail.com%3E
> 
> and the result is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAAbkU4S_G-BmQ3jzjFbz%2BBtGQC-az_CjKwPM7usCWwBdBp8%2B0w%40mail.gmail.com%3E
> 
> We ask the IPMC to vote on this release.
> 
> The artifacts to be voted on are located at:
> https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/
> 
> The hashes of the artifacts are as follows:
> MD5: 45 4C 7A BB 17 C7 D6 47  77 85 92 58 59 DF B7 F5
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dinhtta.asc
> 
> and the signature file is:
> https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/apache-singa-incubating-0.3.0-RC3.tar.gz.asc
> 
> The Github tag is at:
> https://github.com/apache/incubator-singa/releases/tag/v0.3.0-rc3
> 
> with commit ID: d547a861068973db7d8fc82f9c733e95307a40f1
> 
> To check the license, you can use the Apache Rat tool following
> ```
> ./configure
> make rat
> ```
> The result is in rat_check file.
> 
> The vote is open for at least 72 hours, or until the necessary number of
> votes (3 +1) is reached.
> 
> [ ] +1 Release this package as Apache SINGA 0.3.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> Regards,
> Anh.


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

Re: [VOTE] Graduate Apex from the Incubator

[Alan Gates]

+1.

Alan.

> On Mar 28, 2016, at 14:46, Pramod Immaneni  wrote:
> 
> Sorry missed including the resolution. Here is the full email again..
> 
> The Apache Apex community has discussed and voted on graduation to top
> level project.
> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
> 
> Maturity Assessment:http://apex.incubator.apache.org/maturity.html
> Discussion:https://s.apache.org/qrvY
> Vote:https://s.apache.org/R8MR
> Result:https://s.apache.org/sJIC
> 
> Please vote on the resolution pasted below to graduate Apache Apex
> from the incubator to top level project.
> 
> [ ] +1 Graduate Apache Apex from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Apex from the Incubator because…
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> 
> Pramod Immaneni, for the Apache Apex PPMC
> 
> 
> 
> Apache Apex top-level project resolution:
> =
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to Hadoop native, distributed,
> large-scale, high throughput, low-latency, fault tolerant,
> easily operable, unified stream and batch processing platform.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Apex Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Apex Project be and hereby is
> responsible for the creation and maintenance of software
> related to Hadoop native, distributed, large-scale,
> high throughput, low-latency, fault tolerant, easily operable,
> unified stream and batch processing platform;
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Apex" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Apex Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Apex Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Apex Project:
> 
> * Ilya Ganelin 
> * P. Taylor Goetz 
> * Gaurav Gupta 
> * Pramod Immaneni 
> * Amol Kekre 
> * Justin Mclean 
> * Chetan Narsude 
> * Chris Nauroth 
> * Vlad Rozov 
> * Hitesh Shah 
> * Thomas Weise 
> * David Yan 
> * Brennon York 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
> be appointed to the office of Vice President, Apache Apex, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
> 
> RESOLVED, that the initial Apache Apex PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Apex Project; and be it further
> 
> RESOLVED, that the Apache Apex Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Apex podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Apex podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning  wrote:
> 
>> There hasn't been a discussion thread here on the general list, but I am
>> still prepared to vote in favor of this.
>> 
>> +1
>> 
>> See!
>> 
>> I just did.
>> 
>> 
>> 
>> On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni 
>> wrote:
>> 
>>> The Apache Apex community has discussed and voted on graduation to top
>>> level project.
>>> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
>>> 
>>> Maturity Assessment:
>>> http://apex.incubator.apache.org/maturity.html
>>> Discussion:
>>> https://s.apache.org/qrvY
>>> Vote:
>>> https://s.apache.org/R8MR
>>> Result:
>>> https://s.apache.org/sJIC
>>> 
>>> Please vote on the resolution pasted below to graduate Apache Apex
>>> from the incubator to top level project.
>>> 
>>> [ ] +1 Graduate Apache Apex from the Incubator.
>>> [ ] +0 Don't care.
>>> [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
>>> 
>>> This vote will be open for at 

Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)

[Alan Gates]

Forwarding my +1 from the vote on the dev list.

Alan.

> On Mar 6, 2016, at 16:18, Madhan Neethiraj <mad...@apache.org> wrote:
> 
> Incubator PMC,
> 
> Apologies for yet another location-change of the release artifacts. The 
> artifacts are moved from https://dist.apache.org/repos/dist/release to 
> https://dist.apache.org/repos/dist/dev; please use the new location given 
> below. John - thanks for your guidance.
> 
> Artifacts for this release are given below:
>  - Git tag for the release: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>  - Sources for the release: 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
>  - Source release verification:
>  - PGP Signature:   
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
>  - MD5/SHA  Hash:  
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.mds
>  - Keys to verify the signature of the release artifact are available at:  
> https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
> 
> 
> Please review and vote.
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes is reached.
>  [  ] +1  approve
>  [  ] +0  no opinion
>  [  ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding).
> 
> There is already one binding +1 vote from Alan Gates.
> 
> 
> 
> Thanks,
> Madhan
> 
> 
> 
> From: John D. Ament <johndam...@apache.org>
> Sent: Sunday, March 6, 2016 5:50 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)
> 
> To clarify ( to avoid any possibility of confusion ), your release under
> vote goes to
> 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/
> 
> Once its approved, it goes to
> 
> https://dist.apache.org/repos/dist/release/incubator/ranger/
> 
> In addition, you should keep both of these directories clean, dev only
> contains the release under vote, dist only contains the last successful
> release.
> 
> John
> 
> 
> 
> 
> 
> 
> On 3/6/16, 5:45 AM, "Madhan Neethiraj" <mad...@apache.org> wrote:
> 
>> Incubator PMC,
>> 
>> The release artifacts are now available under https://dist.apache.org. 
>> Please use the new locations given below. 
>> 
>> Artifacts for this release are given below:
>> - Git tag for the release: 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>> - Sources for the release: 
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
>> - Source release verification:
>>   - PGP Signature:   
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
>>   - MD5/SHA  Hash:  
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.mds
>>   - Keys to verify the signature of the release artifact are available at:  
>> https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
>> 
>> 
>> 
>> Thanks,
>> Madhan
>> 
>> 
>> 
>> On 2/29/16, 3:44 PM, "Madhan Neethiraj" <mad...@apache.org> wrote:
>> 
>>> Incubator PMC,
>>> 
>>> The Apache Ranger community has voted on and approved the proposal to 
>>> release Apache Ranger 0.5.2 (incubating). The voting result is available at 
>>> http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201602.mbox/%3c62fd4d6f-2a7e-4b7a-b9ce-347f868c2...@apache.org%3e.
>>>  
>>> 
>>> Prior releases of Apache Ranger (incubating) are:
>>> - Apache Ranger 0.5.1 Jan 2016
>>> - Apache Ranger 0.5.0 Jul 2015
>>> - Apache Ranger 0.4.0 Nov 2014
>>> 
>>> 
>>> Artifacts for this release are given below:
>>> - Git tag for the release: 
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>>> - Sources for the release: 
>>> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz
>>> - Source release verification:
>>>   - PGP Signature:   
>>> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz.asc
>>>   - MD5/SHA  Ha

Re: [VOTE] Accept Tephra into the Apache Incubator

[Alan Gates]

rew Purtell and
> Poorna Chandra.
> 
> 
> == Alignment ==
> 
> The ASF is the natural choice to host the Tephra project as its goal of
> encouraging community-driven open source projects fits with our vision for
> Tephra.
> 
> Additionally, many other projects with which we are familiar and expect
> Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and others
> mentioned in the External Dependencies section are Apache projects, and
> Tephra will benefit by close proximity to them.
> 
> = Known Risks =
> 
> == Orphaned Products ==
> 
> There is very little risk of Tephra being orphaned, as it is a key part of
> Cask Data’s products. The core Tephra developers plan to continue to work
> on Tephra, and Cask Data has funding in place to support their efforts
> going forward.
> Also with Phoenix using Tephra for transactions, Phoenix developers are
> keen on contributing to Tephra.
> 
> 
> == Inexperience with Open Source ==
> 
> Several of the core developers have experience with open source
> development. Andreas Neumann is an Apache committer for Oozie and Twill.
> Terence Yim is an Apache committer for Helix and Twill. Poorna Chandra
> is an Apache committer for Twill. Gary Helmling is a committer for
> Apache Twill and a committer and PMC member for Apache HBase.
> James Taylor is PMC chair for Apache Phoenix, PMC member of Apache Calcite,
> and an IPMC member.
> 
> == Homogeneous Developers ==
> 
> The current core developers are all Cask Data employees. However, we
> intend to establish a developer community that includes independent and
> corporate contributors. We are encouraging new contributors via our mailing
> lists, public presentations, and personal contacts, and we will continue to
> do so.
> 
> Apache Phoenix developers have already contributed several patches to Tephra,
> and have expressed interest in becoming long term contributors.
> 
> == Reliance on Salaried Developers ==
> 
> Currently, these developers are paid to work on Tephra. Once the project has
> built a community, we expect to attract committers, developers and community
> other than the current core developers. However, because Cask Data
> products use Tephra internally, the reliance on salaried developers is
> unlikely to change, at least in the near term.
> 
> == Relationships with Other Apache Products ==
> 
> Tephra is deeply integrated with Apache projects. Tephra provides transactions
> over Apache HBase, and uses Apache Twill and Apache Zookeeper for 
> coordination.
> A number of other Apache projects are Tephra dependencies, and are
> listed in the External Dependencies section.
> 
> In addition, Apache Phoenix is using Tephra as the transaction engine.
> 
> == An Excessive Fascination with the Apache Brand ==
> 
> While we respect the reputation of the Apache brand and have no doubt that
> it will attract contributors and users, our interest is primarily to give
> Tephra a solid home as an open source project following an established
> development model. We have also given additional reasons in the Rationale
> and Alignment sections.
> 
> = Documentation =
> 
> The current documentation for Tephra is at https://github.com/caskdata/tephra.
> 
> = Initial Source =
> 
> Tephra codebase is currently hosted at https://github.com/caskdata/tephra.
> 
> = Source and Intellectual Property Submission Plan =
> 
> Tephra codebase is currently licensed under Apache 2.0 license.
> Cask Data owns the trademark for "Tephra". As part of the incubation process
> Cask Data will transfer the trademark to Apache Foundation.
> 
> = External Dependencies =
> 
> The dependencies all have Apache-compatible licenses:
> * dropwizard metrics (Apache 2.0)
> * fastutil (Apache 2.0)
> * gson (Apache 2.0)
> * guava-libraries (Apache 2.0)
> * guice (Apache 2.0)
> * hadoop (Apache 2.0)
> * hbase (Apache 2.0)
> * hdfs (Apache 2.0)
> * junit (EPL v1.0)
> * logback (EPL v1.0 )
> * slf4j (MIT)
> * thrift (Apache 2.0)
> * twill (Apache 2.0)
> * zookeeper (Apache 2.0)
> 
> = Cryptography =
> 
> Tephra does not use cryptography itself, however it can run on secure Hadoop,
> which uses Kerberos.
> 
> = Required Resources =
> 
> == Mailing Lists ==
> 
> * tephra-private for private PMC discussions (with moderated subscriptions)
> * tephra-dev for technical discussions among contributors
> * tephra-commits for notification about commits
> 
> == Subversion Directory ==
> 
> Git is the preferred source control system: git://git.apache.org/tephra
> 
> == Issue Tracking ==
> 
> JIRA Tephra (TEPHRA)
> 
> == Other Resources ==
> 
> The existing code already has un

Re: [VOTE] Apache Apex Malhar Release 3.3.1-incubating (RC1)

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.

> On Feb 29, 2016, at 19:27, Hitesh Shah  wrote:
> 
> +1 - carried over from dev list (binding)
> 
> thanks
> — Hitesh
> 
> 
> On Feb 28, 2016, at 9:53 AM, Bhupesh Chawda  wrote:
> 
>> Hi,
>> 
>> Please vote on the following Apache Apex Malhar 3.3.1-incubating release
>> candidate.
>> 
>> The Apache Apex PPMC has voted to release this candidate.
>> 
>> The community vote passed with 4 binding votes. There were another 3
>> committer votes in favor of the release.
>> 
>> PPMC vote call:
>> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAHvM9d2ZWZAvyhZcWGsKQBQHc_O%2BbC%2BexnppXU8FYyjiWsL8PA%40mail.gmail.com%3E
>> 
>> PPMC vote result:
>> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAHvM9d01_jUQhtQPSGj11dwWwUqUg2dBfMwKjuxDL2EHBUizRg%40mail.gmail.com%3E
>> 
>> This is a source release with binary artifacts published to Maven.
>> 
>> List of all issues fixed: https://s.apache.org/E2rj
>> 
>> Staging directory:
>> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.1-incubating-RC1/
>> Source zip:
>> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.1-incubating-RC1/malhar-3.3.1-incubating-source-release.zip
>> Source tar.gz:
>> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.1-incubating-RC1/malhar-3.3.1-incubating-source-release.tar.gz
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapacheapex-1008
>> 
>> Git source:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.3.1-incubating-RC1
>> (commit: a2a3a0f976f153c6bda83586f6f4df01b596c616)
>> 
>> PGP key:
>> http://pgp.mit.edu:11371/pks/lookup?op=vindex=bhup...@apache.org
>> KEYS file:
>> https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
>> 
>> More information at:
>> http://apex.incubator.apache.org
>> 
>> Please try the release and vote; vote will be open for at least 72 hours.
>> 
>> Thanks,
>> Bhupesh
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Release Apache Apex Core 3.3.0-incubating (RC2)

[Alan Gates]

Forwarding my +1 from the dev list.

Alan.


Thomas Weise 
February 4, 2016 at 0:36
Hi,

Please vote on the following Apache Apex Core 3.3.0-incubating release
candidate.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 5 binding votes from the PPMC (including 3
votes from IPMC members). There were another 11 committer votes in 
favor of

the release.

PPMC vote call:
http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDPjMAZc8-NjjyMgtJGDpHkhVpxv8PYnryfiF4zZZufVmA%40mail.gmail.com%3E

PPMC vote result:
http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201602.mbox/%3CCAKJfLDN4CUVn9cgVhAhqeojP4hDUhwjnWRgXD226VOOBPphmUg%40mail.gmail.com%3E

This is a source release with binary artifacts published to Maven.

List of all issues fixed: http://s.apache.org/wUB

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC2/apex-3.3.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1006/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.3.0-incubating-RC2
(commit: 5f216a1bd27a94785c9ccada78101f892be95cbe)

PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org

Please try the release and vote; vote will be open for at least 72 hours.

Thanks,
Thomas

Re: [VOTE] Release Apache Ranger 0.5.1 (incubating)

[Alan Gates]

Forwarding my +1 from the vote on dev@ranger.

Alan.


Madhan Neethiraj 
January 17, 2016 at 12:21
Incubator PMC,

Please use https://people.apache.org/keys/group/incubator.asc for the 
keys to verify the signature, instead of the location given earlier 
(https://people.apache.org/keys/group/ranger.asc).


Thanks,
Madhan





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

Madhan Neethiraj 
January 14, 2016 at 13:46
Incubator PMC,

The Apache Ranger community has voted on and approved the proposal to 
release Apache Ranger 0.5.1 (incubating). The voting result is 
available at 
http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201601.mbox/%3cab1cffbc-e050-4597-b46c-185d2d4d9...@apache.org%3e. 



Prior releases of Apache Ranger (incubating) are:
- Apache Ranger 0.5.0 Jul 2015
- Apache Ranger 0.4.0 Nov 2014


Artifacts for this release are given below:
- Git tag for the release: 
https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.1-rc2
- Sources for the release: 
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz

- Source release verification:
- PGP Signature: 
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz.asc
- MD5/SHA Hash: 
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz.mds
- Keys to verify the signature of the release artifact are available 
at: https://people.apache.org/keys/group/ranger.asc



Please review and vote.


The vote will be open for at least 72 hours or until necessary number 
of votes is reached.

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

Here is my +1 (non binding)

Thanks
Madhan



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

Re: [VOTE] Apache Apex Malhar Release 3.2.0-incubating (RC2)

[Alan Gates]

+1, see dev vote thread for details of checking I did.

Alan.


Thomas Weise 
November 13, 2015 at 21:30
Hi,

Please vote on the following Apache Apex Malhar 3.2.0-incubating release
candidate. This is the first release of the Malhar library in ASF and 
it is

based on Apex core 3.2.0-incubating. This is a source release.

The Apache Apex PPMC has voted to release this candidate.

The community vote passed with 14 binding votes from the PPMC (including 3
votes from IPMC members).

PPMC vote call:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDMWgzncdN7-nxXksE3F2p3xLfCu%2B_nNL-q6p-H_kwASdA%40mail.gmail.com%3E

PPMC vote result:

http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201511.mbox/%3CCAKJfLDPnu2vJZyt%3D9JNmt3nG_nHYk%2B3AseE__SN%3DKXmJ5AskeQ%40mail.gmail.com%3E

List of all issues fixed: http://s.apache.org/2fZ

Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2
Source zip:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev/incubator/apex/malhar/v3.2.0-incubating-RC2/malhar-3.2.0-incubating-source-release.tar.gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1003/

Git source:
https://git-wip-us.apache.org/repos/asf?p=incubator-apex-malhar.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
(commit:
ff0b0d080ebd8d00cee47321df90dad9357bbead)

PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS

More information at:
http://apex.incubator.apache.org

Please try the release and vote; vote will close after 72 hours.

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

http://www.apache.org/foundation/voting.html

Please add (binding) if your vote is binding.

Thanks,
Thomas

Re: [VOTE] Release Apache SINGA 0.1.0 (incubating)

[Alan Gates]

+1

I looked at the signatures, the LICENSE, NOTICE, and DISCLAIMER files, 
checked for any binary files in the distro, and checked that source 
files have the appropriate license header.


Alan.


Wang Wei 
September 29, 2015 at 19:47
Hi all,

The SINGA community has voted on and approved a proposal to release Apache
SINGA 0.1.0 (incubating).

The vote thread is at:
http://mail-archives.apache.org/mod_mbox/singa-dev/201509.mbox/%3CCAJz0iLsZRgSuPyrMitpt5EdXvaqf4%2BDiF00Xyg2SLb3YEqkDMw%40mail.gmail.com%3E

and the result is at:
http://mail-archives.apache.org/mod_mbox/singa-dev/201509.mbox/%3CCAJz0iLtGNDT8O31V9QOhrapzFf8Nt0XSjckGR%2BxFHrfrFKraPA%40mail.gmail.com%3E

We ask the IPMC to vote on this release.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/singa/

The hashes of the artifacts are as follows:
apache-singa-incubating-0.1.0-RC2.tar.gz.md5: 63 0F DF E0 74 E0 E1 1F 89
F6 0E DF 9E 66 50 73
apache-singa-incubating-0.1.0-RC2.tar.gz.sha256: EE7CF820 70DB46F5 
20FC39A1

F85B5B73 865503BD 36280917 5369EB9F 5FA7199E

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/dinhtta.asc

and the signature file is:
apache-singa-incubating-0.1.0-RC2.tar.gz.asc


The vote is open for at least 72 hours, or until the necessary number of
votes (3 +1) is reached.

[ ] +1 Release this package as Apache SINGA 0.1.0-incubating
[ ] 0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Thanks.

Regards,
Wei Wang

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Alan Gates]

+1.

Alan.


Julian Hyde <mailto:jh...@apache.org>
September 14, 2015 at 18:56
This is a vote for Calcite to become a top-level project.

Since joining the Incubator in May, 2014, the Calcite
community has:
* Produced eight IPMC-approved releases under two release
managers;
* Added five new committers and one new PPMC member;
* Collaborated successfully with several other Apache
projects (Drill, Hive, Kylin, Phoenix, Samza);
* Grown into an active community (typical monthly activity
is 100 emails, 30 commits and 20 issues fixed);
* Conducted a successful community vote to graduate with
20 +1 votes, of which 2 were from our mentors, 12 were
from committers, and 6 were from IPMC members.

Further information: the discussion on the dev list [1],
vote thread [2] and result [3]. Also relevant are the
incubation status page [4] and a thread on this list
requesting review of whether Calcite met the criteria to
graduate [5].

Below is our proposed resolution for the Board.

Please vote:

[ ] +1 Graduate Apache Calcite as a top-level project
[ ] +0
[ ] -1 Do not graduate Apache Calcite because…

Here is my vote:
+1 (binding)

Voting will last 72 hours, ending at 19:00 Pacific on
September 17th.

Julian Hyde, on behalf of Calcite PPMC

[1] http://s.apache.org/ZPC
[2] http://s.apache.org/rvB
[3] http://s.apache.org/sv
[4] http://incubator.apache.org/projects/calcite.html
[5] http://s.apache.org/itP

- - - snip - - -

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to parsing and planning queries on data in a
wide variety of formats.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Calcite
Project", be and hereby is established pursuant to Bylaws of
the Foundation; and be it further

RESOLVED, that the Apache Calcite Project be and hereby is
responsible for the creation and maintenance of software
related to parsing and planning queries on data in a wide
variety of formats; and be it further

RESOLVED, that the office of "Vice President, Apache
Calcite" be and hereby is created, the person holding such
office to serve at the direction of the Board of Directors
as the chair of the Apache Calcite Project, and to have
primary responsibility for management of the projects within
the scope of responsibility of the Apache Calcite Project;
and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Calcite Project:

* Alan Gates 
* Aman Sinha 
* Ashutosh Chauhan 
* James R. Taylor 
* Jacques Nadeau 
* Jesús Camacho Rodríguez 
* Jinfeng Ni 
* John Pullokkaran 
* Julian Hyde 
* Nick Dimiduk 
* Steven Noels 
* Ted Dunning 
* Vladimir Sitnikov 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde be
appointed to the office of Vice President, Apache Calcite,
to serve in accordance with and subject to the direction of
the Board of Directors and the Bylaws of the Foundation
until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the Apache Calcite Project be and hereby is
tasked with the migration and rationalization of the Apache
Incubator Calcite podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Calcite podling encumbered upon the Apache
Incubator Project are hereafter discharged.

- - - end - - -


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

Re: [VOTE] Release apache-calcite-1.4.0-incubating

[Alan Gates]

Forwarding my +1 from the Calcite vote.

Alan.


Jacques Nadeau 
August 28, 2015 at 14:32
Hi all,

The Calcite community has voted on and approved a proposal to release
Apache Calcite 1.4.0-incubating.

Proposal:
http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201508.mbox/%3CCAKa9qD%3DWA1s03rUEuCUbUbWiBgmC_9N%3D1r39dXjLAKevRt6UCQ%40mail.gmail.com%3E

Vote result:
8 binding +1 votes
1 non-binding +1 votes
No -1 votes
http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201508.mbox/%3CCAKa9qD%3DPUH70eyPY3u25O4ayimwOXfBBxiX2txUEcNbUCYODXg%40mail.gmail.com%3E

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/0c0c203daec56c05b6c75fa3896c8af19844df68

Its hash is 0c0c203daec56c05b6c75fa3896c8af19844df68.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/calcite/apache-calcite-1.4.0-incubating-rc0

The hashes of the artifacts are as follows:
src.tar.gz.md5 e052e2b1ffdbdab9eaeb30f4ac838e75
src.tar.gz.sha1 fd979e8b330bb0d3b9be8625c95589e0eb358722
src.zip.md5 ef1880617f3b6415c5e3779d9c2bbc10
src.zip.sha1 b865a9a45046a339c53834e7abea7a7a55927f07

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1009

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jacques.asc

Pursuant to the Releases section of the Incubation Policy and with
the endorsement of 2 of our mentors we would now like to request
the permission of the Incubator PMC to publish the release. The vote
is open for 72 hours, or until the necessary number of votes (3 +1)
is reached.

[ ] +1 Release this package as Apache Calcite 1.4.0-incubating
[ ] -1 Do not release this package because...

Jacques Nadeau, on behalf of Apache Calcite PPMC

Re: [VOTE] Accept HAWQ into the Apache Incubator

[Alan Gates]

 immediately after Incubator PMC
approves HAWQ joining the Incubator and will be licensed under the
Apache License v2.

== Source and Intellectual Property Submission Plan ==
As soon as HAWQ is approved to join the Incubator, the source code
will be transitioned via an exhibit to Pivotal's current Software
Grant Agreement onto ASF infrastructure and in turn made available
under the Apache License, version 2.0. We know of no legal
encumberments that would inhibit the transfer of source code to the
ASF.

== External Dependencies ==

Runtime dependencies:
* gimli (BSD)
* openldap (The OpenLDAP Public License)
* openssl (OpenSSL License and the Original SSLeay License, BSD style)
* proj (MIT)
* yaml (Creative Commons Attribution 2.0 License)
* python (Python Software Foundation License Version 2)
* apr-util (Apache Version 2.0)
* bzip2 (BSD-style License)
* curl (MIT/X Derivate License)
* gperf (GPL Version 3)
* protobuf (Google)
* libevent (BSD)
* json-c (https://github.com/json-c/json-c/blob/master/COPYING)
* krb5 (MIT)
* pcre (BSD)
* libedit (BSD)
* libxml2 (MIT)
* zlib (Permissive Free Software License)
* libgsasl (LGPL Version 2.1)
* thrift (Apache Version 2.0)
* snappy (Apache Version 2.0 (up to 1.0.1)/New BSD)
* libuuid-2.26 (LGPL Version 2)
* apache hadoop (Apache Version 2.0)
* apache avro (Apache Version 2.0)
* glog (BSD)
* googlemock (BSD)

Build only dependencies:
* ant (Apache Version 2.0)
* maven (Apache Version 2.0)
* cmake (BSD)

Test only dependencies:
* googletest (BSD)

Cryptography N/A

== Required Resources ==

=== Mailing lists ===
* priv...@hawq.incubator.apache.org (moderated subscriptions)
* comm...@hawq.incubator.apache.org
* d...@hawq.incubator.apache.org
* iss...@hawq.incubator.apache.org
* u...@hawq.incubator.apache.org

=== Git Repository ===
https://git-wip-us.apache.org/repos/asf/incubator-hawq.git

=== Issue Tracking ===
JIRA Project HAWQ (HAWQ)

=== Other Resources ===

Means of setting up regular builds for HAWQ on builds.apache.org will
require integration with Docker support.

== Initial Committers ==
* Lirong Jian
* Hubert Huan Zhang
* Radar Da Lei
* Ivan Yanqing Weng
* Zhanwei Wang
* Yi Jin
* Lili Ma
* Jiali Yao
* Zhenglin Tao
* Ruilong Huo
* Ming Li
* Wen Lin
* Lei Chang
* Alexander V Denissov
* Newton Alex
* Oleksandr Diachenko
* Jun Aoki
* Bhuvnesh Chaudhary
* Vineet Goel
* Shivram Mani
* Noa Horn
* Sujeet S Varakhedi
* Junwei (Jimmy) Da
* Ting (Goden) Yao
* Mohammad F (Foyzur) Rahman
* Entong Shen
* George C Caragea
* Amr El-Helw
* Mohamed F Soliman
* Venkatesh (Venky) Raghavan
* Carlos Garcia
* Zixi (Jesse) Zhang
* Michael P Schubert
* C.J. Jameson
* Jacob Frank
* Ben Calegari
* Shoabe Shariff
* Rob Day-Reynolds
* Mel S Kiyama
* Charles Alan Litzell
* David Yozie
* Ed Espino
* Caleb Welton
* Parham Parvizi
* Dan Baskette
* Christian Tzolov
* Tushar Pednekar
* Greg Chase
* Chloe Jackson
* Michael Nixon
* Roman Shaposhnik
* Alan Gates
* Owen O'Malley
* Thejas Nair
* Don Bosco Durai
* Konstantin Boudnik
* Sergey Soldatov
* Atri Sharma

== Affiliations ==
* Barclays: Atri Sharma
* Bloomberg: Justin Erenkrantz
* Hortonworks: Alan Gates, Owen O'Malley, Thejas Nair, Don Bosco Durai
* WANDisco: Konstantin Boudnik, Sergey Soldatov
* Pivotal: everyone else on this proposal

== Sponsors ==

=== Champion ===
Roman Shaposhnik

=== Nominated Mentors ===

The initial mentors are listed below:
* Alan Gates - Apache Member, Hortonworks
* Owen O'Malley - Apache Member, Hortonworks
* Thejas Nair - Apache Member, Hortonworks
* Konstantin Boudnik - Apache Member, WANDisco
* Roman Shaposhnik - Apache Member, Pivotal
* Justin Erenkrantz - Apache Member, Bloomberg

=== Sponsoring Entity ===
We would like to propose Apache incubator to sponsor this project.

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

Re: [VOTE] Accept Apex into the Apache Incubator

[Alan Gates]

 into their own repos. Two repos will reflect clear
 separation of engine (Apex) and operators/business logic (Malhar). It
 will allow or independent release cycles (operator change independent
 of engine due to stable API). We however do not believe in two levels
 of committers. We believe there should be one community that works
 across both and innovates with ideas that Malhar and Apex combined
 provide the value proposition. We are proposing that Apache incubation
 process help us to foster development of one community (mailing list,
 committers), and a yet be ok with two repos. We are proposing that
 this be taken up during incubation. Community will learn if this
 works. The decision on whether to split them into two projects be
 taken after the learning curve during incubation.

 == Initial Committers ==
 * Roma Ahuja (rahuja at directv dot com)
 * Isha Arkatkar (isha at datatorrent dot com)
 * Raja Ali (raji at silverspringnet dot com)
 * Sunaina Chaudhary ( SChaudhary at directv dot com)
 * Bhupesh Chawda (bhupesh at datatorrent dot com)
 * Chaitanya Chelobu (chaitanya at datatorrent dot com)
 * Bright Chen (bright at datatorrent dot com)
 * Pradeep Dalvi (pradeep dot dalvi at datatorrent dot com)
 * Sandeep Deshmukh (sandeep at datatorrent dot com)
 * Yogi Devendra (yogi at datatorrent dot com)
 * Cem Ezberci (hasan dot ezberci at ge dot com)
 * Timothy Farkas (tim at datatorrent dot com)
 * Ilya Ganelin (ilya dot ganelin at capitalone dot com)
 * Vitthal Gogate (vitthal_gogate at yahoo dot com)
 * Parag Goradia (parag dot goradia at ge dot com)
 * Tushar Gosavi (tushar at datatorrent dot com)
 * Priyanka Gugale (priyanka at datatorrent dot com)
 * Gaurav Gupta (gaurav at datatorrent dot com)
 * Sandesh Hegde (sandesh at datatorrent dot com)
 * Siyuan Hua ( siyuan at datatorrent dot com)
 * Ajith Joseph (ajoseph at silverspring dot com)
 * Amol Kekre ( amol at datatorrent dot com)
 * Chinmay Kolhatkar ( chinmay at datatorrent dot com)
 * Pramod Immaneni ( pramod at datatorrent dot com)
 * Anuj Lal ( anuj dot lal at ge dot com)
 * Dongsu Lee (dlee3 at directv dot com)
 * Vitaly Li (blossom dot valley at gmail dot com)
 * Dean Lockgaard (dean at datatorrent dot com)
 * Rohan Mehta (rohan_mehta at apple dot com)
 * Adi Mishra (apmishra at directv dot com, adi dot mishra at gmail dot
 com)
 * Chetan Narsude (chetan at datatorrent dot com)
 * Darin Nee (dnee at silverspring dot com)
 * Alexander Parfenov (sasha at datatorrent dot com)
 * Andrew Perlitch (andy at datatorrent dot com)
 * Shubham Phatak (shubham at datatorrent dot com)
 * Ashwin Putta (ashwin at datatorrent dot com)
 * Rikin Shah (shah_rikin at yahoo dot com)
 * Luis Ramos (l dot ramos at ge dot com)
 * Munagala Ramanath (ram at datatorrent dot com)
 * Vlad Rozov (vlad dot rozov at datatorrent dot com)
 * Atri Sharma (atri dot jiit at gmail dot com)
 * Chandni Singh (chandni at datatorrent dot com)
 * Venkatesh Sivasubramanian (venkateshs at ge dot com)
 * Aniruddha Thombare (aniruddha at datatorrent dot com)
 * Jessica Wang (jessica at datatorrent dot com)
 * Thomas Weise (thomas at datatorrent dot com)
 * David Yan (david at datatorrent dot com)
 * Kevin Yang (yang dot k at ge dot com)
 * Brennon York (brennon dot york at capitalone dot com)

 == Affiliations ==
 * Apple: Vitaly Li, Rohan Mehta
 * Barclays: Atri Sharma
 * Class Software: Justin Mclean
 * CapitalOne: Ilya Ganelin, Brennon York
 * DataTorrent: everyone else on this proposal
 * Datachief: Rikin Shah
 * DirecTV: Roma Ahuja, Sunaina Chaudhary, Dongsu Lee, Adi Mishra
 * E8security: Vitthal Gogate
 * General Electric: Cem Ezberci, Parag Goradia, Anuj Lal, Luis Ramos,
 Venkatesh Sivasubramanian, Kevin Yang
 * Hortonworks: Alan Gates, Taylor Goetz, Chris Nauroth, Hitesh Shah
 * MapR: Ted Dunning
 * SilverSpring Networks: Raja Ali, Ajith Joseph, Darin Nee

 == Sponsors ==

 === Champion ===
 Ted Dunning

 === Nominated Mentors ===

 The initial mentors are listed below:
 * Ted Dunning - Apache Member, MapR
 * Alan Gates - Apache Member, Hortonworks
 * Taylor Goetz - Apache Member, Hortonworks
 * Justin Mclean - Apache Member, Class Software
 * Chris Nauroth - Apache Member, Hortonworks
 * Hitesh Shah: Apache Member, Hortonworks

 === Sponsoring Entity ===

 We would like to propose Apache incubator to sponsor this project.

 P. Taylor Goetz mailto:ptgo...@apache.org
 August 13, 2015 at 7:48
 Following the discussion thread [1], I would like to call a VOTE for
 Accepting Apex as a new Apache Incubator project.

 The proposal is available on the wiki [2] and is also attached below.

 The VOTE will be open for at least 72 hours.

 [ ] +1 Accept Apex into the Incubator
 [ ] ±0 No opinion
 [ ] -1 Do not accept Apex into the Incubator because…

 Thanks,

 -Taylor

 [1] http://s.apache.org/apex_discuss
 [2] https://wiki.apache.org/incubator/ApexProposal


 == Abstract ==
 Apex is an enterprise grade native YARN big data-in-motion platform
 that unifies stream processing as well as batch processing

Re: [VOTE] Release Apache SAMOA 0.3.0 (incubating)

[Alan Gates]

Forwarding my +1 from the samoa dev list.

Alan.


Gianmarco De Francisci Morales mailto:g...@apache.org
July 9, 2015 at 2:29
Hi,

The SAMOA PPMC has voted to release SAMOA 0.3.0 (incubating).
The vote passed with 5 +1 (binding) votes and no 0/-1 votes.

Here the vote thread: http://s.apache.org/41R

Here a summary of the info for the RC:
-
The commit to be voted on is in the branch releases/0.3.0-incubating
(commit 15c047a16b7e8db412d4d83c79ed5f54c702974d):
https://git1-us-west.apache.org/repos/asf?p=incubator-samoa.git;a=commit;h=15c047a16b7e8db412d4d83c79ed5f54c702974d

Tag v0.3.0-incubating:
https://git1-us-west.apache.org/repos/asf?p=incubator-samoa.git;a=tag;h=refs/tags/v0.3.0-incubating

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/gdfm.asc

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/staging/org/apache/samoa/samoa/0.3.0-incubating/

The source release is available at:
https://dist.apache.org/repos/dist/dev/incubator/samoa/0.3.0-incubating-rc1/
-

Vote is open for the next 72 hours (closes on July 12).

[ ] +1 Release this package as Apache SAMOA 0.3.0 (incubating)
[ ] +0 No opinion
[ ] -1 Do not release this package because ...

Cheers,
--
Gianmarco

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Alan Gates]

+1 (binding).

Alan.


Seetharam Venkatesh mailto:venkat...@innerzeal.com
May 1, 2015 at 0:26
Hello folks,

Following the discussion earlier in the thread: http://s.apache.org/r2

I would like to call a VOTE for accepting Apache Atlas as a new incubator
project.

The proposal is available at:
https://wiki.apache.org/incubator/AtlasProposal
Also, the text of the latest wiki proposal is included at the bottom of
this email.

The VOTE is open for at least the next 72 hours:

[ ] +1 accept Apache Atlas into the Apache Incubator
[ ] ±0 Abstain
[ ] -1 because...

Of course I am +1! (non-binding)

Thanks!


= Apache Atlas Proposal =

== Abstract ==

Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and 
efficiently

meet their compliance requirements within Hadoop and allows integration
with the complete enterprise data ecosystem.

== Proposal ==

Apache Atlas allows agnostic governance visibility into Hadoop, these
abilities are enabled through a set of core foundational services powered
by a flexible metadata repository.

These services include:

* Search and Lineage for datasets
* Metadata driven data access control
* Indexed and Searchable Centralized Auditing operational Events
* Data lifecycle management – ingestion to disposition
* Metadata interchange with other metadata tools

== Background ==

Hadoop is one of many platforms in the modern enterprise data 
ecosystem and

requires governance controls commensurate with this reality.

Currently, there is no easy or complete way to provide comprehensive
visibility and control into Hadoop audit, lineage, and security for
workflows that require Hadoop and non-Hadoop processing.

Many solutions are usually point based, and require a monolithic
application workflow. Multi-tenancy and concurrency are problematic as
these offerings are not aware of activity outside of their narrow focus.

As Hadoop gains greater popularity, governance concerns will become
increasingly vital to increasing maturity and furthering adoption. It is a
particular barrier to expanding enterprise data under management.

== Rationale ==

Atlas will address issues previously discussed by providing governance
capabilities in Hadoop -- using both a prescriptive and forensic model
enriched by business taxonomical metadata. Atlas, at its core, is
designed to exchange metadata with other tools and processes within and
outside of the Hadoop stack -- enable governance controls that are truly
platform agnostic and effectively (and defensibly) address compliance
concerns.

Initially working with a group of leading partners in several industries,
Atlas is built to solve specific real world governance problems that
accelerate product maturity and time to value.

Atlas aims to grow a community to help build a widely adopted pattern for
governance, metadata modeling and exchange in Hadoop – which will advance
the interests for the whole community.

== Current Status ==

An initial version with a valuable set of features is developed by the 
list

of initial committers and is hosted on github.

=== Meritocracy ===

Our intent with this proposal is to start building a diverse developer
community around Atlas following the Apache meritocracy model. We have
wanted to make the project open source and encourage contributors from
multiple organizations from the start.

We plan to provide plenty of support to new developers and to quickly
recruit those who make solid contributions to committer status.

=== Community ===

We are happy to report that the initial team already represents multiple
organizations. We hope to extend the user and developer base further 
in the

future and build a solid open source community around Atlas.

=== Core Developers ===

Atlas development is currently being led by engineers from Hortonworks –
Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
engineers have deep expertise in Hadoop and are quite familiar with the
Hadoop Ecosystem.

=== Alignment ===

The ASF is a natural host for Atlas given that it is already the home of
Hadoop, Falcon, Hive, Pig, Oozie, Knox, Ranger, and other emerging “big
data” software projects.

Atlas has been designed to solve the data governance challenges and
opportunities of the Hadoop ecosystem family of products as well as
integration to the tradition Enterprise Data ecosystem.

Atlas fills the gap that the Hadoop Ecosystem has been lacking in the 
areas

of data governance and compliance management.

== Known Risks ==

=== Orphaned products  Reliance on Salaried Developers ===
The core developers plan to work full time on the project. There is very
little risk of Atlas getting orphaned. A prototype of Atlas is in use and
being actively developed by several companies and have vested interest in
its continued vitality and adoption.

=== Inexperience with Open Source ===
Many of the core developers are PMC and committers of Apache. Harish 
Butani

is PMC 

Re: [VOTE] Release apache-calcite-1.2.0-incubating

[Alan Gates]

+1.  Checked out the LICENSE, NOTICE, and DISCLAIMER files, checked to 
make sure there were no jars or class files in the source distribution, 
ran the tests (and quickly found the east of GMT issues :) ).


Alan.


Julian Hyde mailto:jh...@apache.org
April 13, 2015 at 6:05
Hi all,

The Calcite community has voted on and approved a proposal to release
Apache Calcite 1.2.0-incubating.

Thanks to everyone who has contributed to this release. This is a 
short release,
less than a month after 1.1, but there are 42 fixed issues 
nevertheless. In

particular, Avatica has better coverage of the JDBC API and is much more
robust. You can read the release notes here:
https://github.com/apache/incubator-calcite/blob/branch-1.2/doc/HISTORY.md

During the vote we noted issue
https://issues.apache.org/jira/browse/CALCITE-677: one test fails if you
run in a time zone east of Greenwich. The bug is minor, but affects the
build process as documented in the HOWTO. After a prolonged debate we
reached consensus that a note accompanying the release announcement was
sufficient.

Proposal:
http://s.apache.org/calcite-1.2-vote

Vote result:
3 binding +1 votes
2 non-binding +1 votes
No -1 votes
http://s.apache.org/calcite-1.2-result

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/d60f2aa3aa9ce7cda7c4f6986af5729d50a28679

Its hash is d60f2aa3aa9ce7cda7c4f6986af5729d50a28679.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/calcite/apache-calcite-1.2.0-incubating-rc1

The hashes of the artifacts are as follows:
src.tar.gz.md5 ead5878c92896668a51ab71a4108b070
src.tar.gz.sha1 9cd0b8c542dd8b1af50661543e6af3c67ad9da82
src.zip.md5 85a547882c800677f46f59444c8a1539
src.zip.sha1 cefa18ab2243814ef8a2cde352d4059c2da3dc28

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1007

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jhyde.asc

Pursuant to the Releases section of the Incubation Policy we would now
like to request the permission of the Incubator PMC to publish the 
release.
The vote is open for 72 hours, or until the necessary number of votes 
(3 +1)

is reached.

[ ] +1 Release this package as Apache Calcite 1.2.0-incubating
[ ] -1 Do not release this package because...

Julian Hyde, on behalf of Apache Calcite PPMC

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

Re: [VOTE] Release apache-calcite-1.1.0-incubating

[Alan Gates]

Forwarding my +1 from dev@calcite:
+1.  I checked the signatures, DISCLAIMER, NOTICE, and LICENSE files, 
built the code and ran the tests, and checked to make sure there were no 
jars or class files in the distribution.


Alan.


Julian Hyde mailto:jh...@apache.org
March 16, 2015 at 23:30
Hi all,

The Calcite community has voted on and approved a proposal to release
Apache Calcite 1.1.0-incubating.

Proposal:
http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3ccamctmekcqb3bezn0q-1ug6tzxm1p6jzjvbun9jupsfnjc3r...@mail.gmail.com%3E

Vote result:
3 binding +1 votes
1 non-binding +1 votes
No -1 votes
http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3CCAMCtmeJ4uRMbZRc8yFUw8JjH_P-geG749%3D-6m%3D2K3tYuutSthQ%40mail.gmail.com%3E

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/f10ea367ff1cc25497f50f149ef0c91b3ae03031

Its hash is f10ea367ff1cc25497f50f149ef0c91b3ae03031.

The artifacts to be voted on are located here:
http://people.apache.org/~jhyde/apache-calcite-1.1.0-incubating-rc1/

The hashes of the artifacts are as follows:
src.tar.gz.md5 805f8a1ec7f7dec0b4cd096a7f2b24c3
src.tar.gz.sha1 bc0e718ce3e75c1975bc1825fca2e0dcb22da3d2
src.zip.md5 41732e764ba9557c2dbf269d7904c61b
src.zip.sha1 d401cf6a1fd539a3167201d5ed2c6dfe31417349

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1006

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jhyde.asc

Pursuant to the Releases section of the Incubation Policy and with
the endorsement of 1 of our mentors we would now like to request
the permission of the Incubator PMC to publish the release. The vote
is open for 72 hours, or until the necessary number of votes (3 +1)
is reached.

[ ] +1 Release this package as Apache Calcite 1.1.0-incubating
[ ] -1 Do not release this package because...

Julian Hyde, on behalf of Apache Calcite PPMC

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

Re: [VOTE] Accept Apache Singa as incubator project

[Alan Gates]

.

=== Relationship with Other Apache Products ===
Apache Mahout and Apache Spark's ML-LIB are general machine learning
systems. Deep
learning algorithm can thus be implemented on these two platforms as
well. However, the there are differences in training efficiency,
scalability and
usability. Mahout and Spark ML-LIB follow models where their
nodes run synchronously. This is the fundamental difference to Singa who
follows the parameter server framework (like Google Brain and Microsoft
Adam). Singa can run synchronously or asynchronously. The asynchronous 
mode

is superior than the synchronous mode in terms of scalability. In
addition, Singa has some optimizations towards deep learning models
(e.g., model
parallelism, data parallelism and hybrid-parallelism) which make Singa
more efficient. We also provide ease of use programming model for deep
learning algorithms.

There are also plans for integration with Apache Hadoop's HDFS as
storage, to handle large training data.
Specifically, we store the training data (e.g., images or raw features of
images) in HDFS, then (pre-)fetch them online.
We will also explore integration with Hadoop's Yarn and Apache Mesos
to do resource management.


== Documentation ==
The project is hosted at
http://www.comp.nus.edu.sg/~dbsystem/project/singa.html.
Documentations can be found at the Github Wiki Page:
https://github.com/nusinga/singa/wiki.
We continue to refine and improve the documentation.

== Initial Source ==
We use Github to maintain our source code, 
https://github.com/nusinga/singa


== Source and Intellectual Property Submission Plan ==
We plan to make our code base be under Apache License, Version 2.0.

== External Dependencies ==
* required by the core code base: glog, gflags, google protobuf,
open-blas, mpich, armci-mpi.
* required by data preparation and preprocessing: opencv, hdfs, python.

== Cryptography ==
Not Applicable

== Required Resources ==
=== Mailing Lists ===
Currently, we use google group for internal discussion. The mailing 
address is

nusi...@googlegroup.com. We will migrate the content to the apache mailing
lists in the future.

* singa-dev
* singa-user
* singa-commits
* singa-private (for private discussion within PCM)

=== Git Repository ===
We want to continue using git for version control. Hence, a git repo
is required.

=== Issue Tracking ===
JIRA Singa (SINGA)

== Initial Committers ==
* Beng Chin Ooi (ooibc @comp.nus.edu.sg)
* Kian Lee Tan (tankl @comp.nus.edu.sg)
* Gang Chen (cg @zju.edu.cn)
* Wei Wang (wangwei @comp.nus.edu.sg)
* Dinh Tien Tuan Anh (dinhtta @comp.nus.edu.sg)
* Jinyang Gao (jinyang.gao @comp.nus.edu.sg)
* Sheng Wang (wangsh @comp.nus.edu.sg)
* Kaiping Zheng (kaiping @comp.nus.edu.sg)
* Zhaojing Luo (zhaojing @comp.nus.edu.sg)
* Zhongle Xie (zhongle @comp.nus.edu.sg)

== Affiliations ==
* Beng Chin Ooi, National University of Singapore
* Kian Lee Tan, National University of Singapore
* Gang Chen, Zhejiang University
* Wei Wang, National University of Singapore
* Dinh Tien Tuan Anh, National University of Singapore
* Jinyang Gao, National University of Singapore
* Sheng Wang, National University of Singapore
* Kaiping Zheng, National University of Singapore
* Zhaojing Luo, National University of Singapore
* Zhongle Xie, National University of Singapore

== Sponsors ==
=== Champion ===
Thejas Nair (thejas at apache.org)

=== Nominated Mentors ===
* Thejas Nair (thejas at apache.org)
* Alan Gates (gates at apache dot org)
* Daniel Dai (daijy at apache dot org)
* Ted Dunning (tdunning at apache dot org)

=== Sponsoring Entity ===
We are requesting the Incubator to sponsor this project.

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

Re: [VOTE] Release Apache Calcite 1.0.0 (incubating)

[Alan Gates]

+1, I checked the keys and signatures, reviewed the LICENSE and NOTICE 
files, checked for any binary contents in the source distribution, 
checked to make sure there were not SNAPSHOT dependencies, and did a 
maven build with a fresh repo.


Alan.


Julian Hyde mailto:jh...@apache.org
February 4, 2015 at 0:40
Hi all,

The Calcite community has voted on and approved a proposal to release
Apache Calcite 1.0.0 (incubating).

Proposal:
http://mail-archives.apache.org/mod_mbox/calcite-dev/201502.mbox/%3CCAMCtme%2B02fa0PPgXes8VEYdHaPN4wwQRNE7HnVM%2BA7E%3DbzD5iA%40mail.gmail.com%3E

Vote result:
4 binding +1 votes
1 non-binding +1 votes
No -1 votes
http://mail-archives.apache.org/mod_mbox/calcite-dev/201502.mbox/%3ccamctmek6ad36qzt9ubq4eexq2vjtqy-29nf-nmvz7rt4m8h...@mail.gmail.com%3E

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/2dd83f21784c4366df84a3aaa62a8b7b0e36d443

Its hash is 2dd83f21784c4366df84a3aaa62a8b7b0e36d443.

The artifacts to be voted on are located here:
http://people.apache.org/~jhyde/apache-calcite-1.0.0-incubating-rc3/

The hashes of the artifacts are as follows:
src.tar.gz.md5 cf64a9421c38959fec9b1802ae39dc66
src.tar.gz.sha1 e1c06d30622e9c16f738d09f1339d60d0388fc62
src.zip.md5 dd389c4c377647fd204a9a3ad83f199a
src.zip.sha1 5ff3b828cb4ea419afa393b7a9f11a294c682a49

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1004

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jhyde.asc

Pursuant to the Releases section of the Incubation Policy we would now
like to request the permission of the Incubator PMC to publish the 
release.
The vote is open for 72 hours, or until the necessary number of votes 
(3 +1)

is reached.

[ ] +1 Release this package as Apache Calcite 1.0.0 incubating
[ ] -1 Do not release this package because...

Forwarding 1 vote from an IPMC member on the PPMC vote:
+1 Brock Noland

Julian Hyde, on behalf of Apache Calcite PPMC

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

Graduation question

[Alan Gates]

As a Flink mentor can I submit the graduation resolution to the board 
now that it has passed, or is that a job for Roman as IPMC chair?


Alan.
--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Graduation question

[Alan Gates]

I've added the resolution to the board agenda for Wednesday's meeting.  
Thanks Marvin for the guidance.


Alan.


Marvin Humphrey mailto:mar...@rectangular.com
December 15, 2014 at 11:20

Short answer: go ahead.

Long answer: There's no role requirement, so in theory literally
anyone could send an email to board@apache with the resolution text.
However, it helps if it's someone who's subscribed to board@apache
(and thus whose messages won't get stuck in moderation) and who has
sufficient privileges to commit changes to the board agenda in svn.
In practice, that means that resolutions tend to be submitted by
Mentors who are also ASF Members subscribed to board@apache.

Marvin Humphrey

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

Alan Gates mailto:ga...@hortonworks.com
December 15, 2014 at 10:36
As a Flink mentor can I submit the graduation resolution to the board 
now that it has passed, or is that a job for Roman as IPMC chair?


Alan.


--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Ranger 0.4.0 (incubating) - (formally known as Apache Argus)

[Alan Gates]

+1, checked LICENSE, NOTICE, and DISCLAIMER, checked signatures, built 
the code, checked for stray .class or .jar files.


Alan.


Selvamohan Neethiraj mailto:sneet...@apache.org
November 13, 2014 at 0:33
The Apache Ranger community has voted on and approved a proposal to 
release Apache Ranger 0.4.0 (incubating).


This will be our first release since the project entered incubation in 
July 2014 as Apache Argus and then, got it renamed as Apache Ranger.


The ranger-0.4.0-rc3 release candidate is now available with the 
following artifacts up for a project vote :


Git tag for the release:
https://git-wip-us.apache.org/repos/asf?p=incubator-argus.git;a=shortlog;h=refs/tags/ranger-0.4.0-rc3

Source release:
http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz 
http://people.apache.org/%7Esneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz


Source release verification:
  PGP Signature: 
http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.asc 
http://people.apache.org/%7Esneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.asc
  MD5/SHA  Hash: 
http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.mds 
http://people.apache.org/%7Esneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.mds
  Keys to verify the signature of the release artifact are available 
at: https://people.apache.org/keys/group/argus.asc


Build verification steps can be found at: 
http://argus.incubator.apache.org/quick_start_guide.html


The vote will be open for at least 72 hours or until necessary number 
of votes are reached.

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

Here is my +1 (non binding)

Thanks
Selva-


--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Calcite 0.9.2 (incubating)

[Alan Gates]

Forwarding my +1 from the dev@calcite list.

Alan.


Julian Hyde mailto:jh...@apache.org
November 9, 2014 at 20:57
Hi all,

The Calcite community has voted on and approved a proposal to release
Apache Calcite 0.9.2 (incubating).

Proposal:
http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201411.mbox/%3CCAMCtme%2BV1wG%3Dqzsht_15p1-8G%2BSxZ-s8NYLTYobsKL513k5J_A%40mail.gmail.com%3E

Vote result:
5 binding +1 votes
0 non-binding +1 votes
No -1 votes
http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201411.mbox/%3CCAMCtmeLbLUyfqZ0JgMEgXUXaXKsyRtOOts972JaxA73dr9My1Q%40mail.gmail.com%3E

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/0404fd236ec78e7f83e047972b190cbc7d4fad6a

Its hash is 0404fd236ec78e7f83e047972b190cbc7d4fad6a.

The artifacts to be voted on are located here:
http://people.apache.org/~jhyde/apache-calcite-0.9.2-incubating-rc1/

The hashes of the artifacts are as follows:
src.tar.gz.md5 2c24981f92d86caa9ea258432342cf97
src.tar.gz.sha1 a97de92ff1be8603d9c5d8402009451a49c5e843
src.zip.md5 533ecc9be0de2fd917f08857ff76fb26
src.zip.sha1 ee0a6a5760ed205f6d7666544b4efe04306c7a68

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1001

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jhyde.asc

Pursuant to the Releases section of the Incubation Policy and with
the endorsement of 2 of our mentors we would now like to request
the permission of the Incubator PMC to publish the release. The vote
is open for 72 hours, or until the necessary number of votes (3 +1)
is reached.

[ ] +1 Release this package as Apache Calcite 0.9.2 incubating
[ ] -1 Do not release this package because...

Julian Hyde, on behalf of Apache Calcite PPMC

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



--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Graduation of Apache Falcon from the Incubator

[Alan Gates]

+1.

Alan.


Jean-Baptiste Onofré mailto:j...@nanthrax.net
November 5, 2014 at 5:48
Hi all,

We wrapped up the vote on the Apache Falcon dev list in which the 
community expressed its desire to graduate to a top-level project.


The vote has passed with:
13 binding +1 votes
8 non-binding +1 votes
no 0 or -1 vote

This is the Incubator vote to decide if Apache Falcon should graduate 
from the Incubator. Please see the resolution later in this e-mail.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Falcon from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Falcon from the Incubator because ...

Thanks,
Regards
JB

 resolution
WHEREAS, the Board of Directors deems it to be in the best interests 
of the Foundation and consistent with the Foundation's purpose to 
establish a Project Management Committee charged with the creation and 
maintenance of open-source software, for distribution at no charge to 
the public, related to Big Data management platform covering data 
pipelines, data motion, data lifecycle management, data discovery  
governance


NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee 
(PMC), to be known as the Apache Falcon Project, be and hereby is 
established pursuant to Bylaws of the Foundation; and be it further


RESOLVED, that the Apache Falcon Project be and hereby is responsible 
for the creation and maintenance of software related to interactive 
analysis of large-scale datasets; and be it further RESOLVED, that the 
office of Vice President, Apache Falcon be and hereby is created, 
the person holding such office to serve at the direction of the Board 
of Directors as the chair of the Apache Falcon Project, and to have 
primary responsibility for management of the projects within the scope 
of responsibility of the Apache Falcon Project; and be it further 
RESOLVED, that the persons listed immediately below be and hereby are 
appointed to serve as the initial members of the Apache Falcon Project:


* Srikanth Sundarrajan sriksun at apache dot org
* Venkatesh Seetharam venkatesh at apache dot org
* Shwetha GS shwethags at apache dot org
* Shaik Idris shaikidris at apache dot org
* Sanjay Radia sanjay at apache dot org
* Sharad Agarwal sharad at apache dot org
* Amareshwari SR amareshwari at apache dot org
* Samarth Gupta samarthg at apache dot org
* Rishu Mehrothra rishumehrothra at apache dot org
* Arpit Gupta arpit at apache dot org
* Suhas Vasu suhas.vasu at apache dot org
* Jean-Baptiste Onofré jbonofre at apache dot org
* Ruslan Ostafiychuk rostafiychuk at apache dot org
* Raghav Kumar Gautam raghav at apache dot org


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be 
appointed to the office of Vice President, Apache Falcon, to serve in 
accordance with and subject to the direction of the Board of Directors 
and the Bylaws of the Foundation until death, resignation, retirement, 
removal or disqualification, or until a successor is appointed; and be 
it further


RESOLVED, that the Apache Falcon Project be and hereby is tasked with 
the migration and rationalization of the Apache Incubator Falcon 
podling; and be it further


RESOLVED, that all responsibilities pertaining to the Apache Incubator
Falcon podling encumbered upon the Apache Incubator Project are 
hereafter discharged.





--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Calcite 0.9.1 (incubating)

[Alan Gates]

+1, forwarded from the PPMC vote.

Alan.


Julian Hyde mailto:jh...@apache.org
October 17, 2014 at 6:49
This vote has been open 8 days, and has two +1 votes. There has been a
lot of discussion, but I don't think any issues have been discovered
which would stop the release. We seem have reached impasse.

I plan to close this vote in 24 hours. If we get one more +1, the vote
will pass. If we don't, I will cancel the vote.

Julian


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

sebb mailto:seb...@gmail.com
October 14, 2014 at 4:57
On 13 October 2014 17:11, Dennis E. Hamiltondennis.hamil...@acm.org  wrote:

I suggest that the release manager and anyone else in the KEYS file should
have added key fingerprints to their Apache profiles athttps://id.apache.org/.

This will have their PGP keys refreshed regularly under their Apache ID at
https://people.apache.org/keys/committer/.

With regard to an identifiable association of the key, presence in this
manner connects the PGP key to The Apache ID by demonstration of control
over the committer's Apache profile.


Similar traceability applies if the user adds their key to the KEYS
file in SVN at

https://dist.apache.org/repos/dist/release/TLP/[path/]KEYS

[This file is required for providing the keys to downloaders]

But no harm in adding the key to LDAP as well.


One can go farther by adding the user...@apache.org to an User-ID on the key.
Verifying that one has control over that e-mail address (and all User-IDs)
Is done by registering the public key at the PGP Global Directory service at
https://keyserver2.pgp.com/vkd/GetWelcomeScreen.event  and completing the
ceremony specified there.  After the ceremony is completed, you can retrieve
your counter-signed PGP key from that service and synchronize it to a public
PGP key server.  The ASF will pick it up on a future refresh.

Use of the key from the Apache ID list has certain valuable properties.  It is
not fixed, as in the key files in the project and in distributions.  That means
any additional (web-of-trust) certifications of the keys association with a
committer are updated automatically.  That includes any revocations.



The keys from the ASF ID list also have disadvantages.
Keys are used to sign artifacts for projects, and need to remain
available whilst the artifact remains available.
That includes archived artifacts.


  -- Dennis E. Hamilton
 dennis.hamil...@acm.org+1-206-779-9430
 https://keybase.io/orcmid  PGP F96E 89FF D456 628A
 X.509 certs used and requested for signed e-mail



-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Sunday, October 12, 2014 22:29
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache Calcite 0.9.1 (incubating)

Hi,


First, the signing key is present in SVN, but has not been uploaded to the
standard key-servers, nor has it been signed by anyone.

I found it here:
https://pgp.mit.edu/pks/lookup?search=Julian+Hydeop=index

Even if the key is part of a web trust it may not be part of everyone's web of 
trust. I'd see that as a hard requirement to meet.

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


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



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

Dennis E. Hamilton mailto:dennis.hamil...@acm.org
October 13, 2014 at 9:11
I suggest that the release manager and anyone else in the KEYS file 
should
have added key fingerprints to their Apache profiles at 
https://id.apache.org/.


This will have their PGP keys refreshed regularly under their Apache 
ID at

https://people.apache.org/keys/committer/.

With regard to an identifiable association of the key, presence in this
manner connects the PGP key to The Apache ID by demonstration of control
over the committer's Apache profile.

One can go farther by adding the user...@apache.org to an User-ID on 
the key.

Verifying that one has control over that e-mail address (and all User-IDs)
Is done by registering the public key at the PGP Global Directory 
service at

https://keyserver2.pgp.com/vkd/GetWelcomeScreen.event and completing the
ceremony specified there. After the ceremony is completed, you can 
retrieve
your counter-signed PGP key from that service and synchronize it to a 
public

PGP key server. The ASF will pick it up on a future refresh.

Use of the key from the Apache ID list has 

Re: [VOTE] Release Apache Flink 0.6.1-incubating

[Alan Gates]

+1.

Alan.


Ufuk Celebi mailto:u...@apache.org
September 19, 2014 at 6:20
Please vote on releasing Apache Flink (incubating) 0.6.1-incubating.

This will be the second release of the Apache Flink project under the
Incubator. Besides minor bug fixes, this release addresses issues 
raised by

Justin Mclean regarding the LICENSE and NOTICE files of the previous
0.6-incubating release.

Vote on d...@flink-incubator.apache.org:
http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201409.mbox/%3CCAKiyyaEd-Db-HwBnwf24wVtJ5FpE0UC1NfQ-0vnQ5SffQ3fSJQ%40mail.gmail.com%3E

Vote result (4 binding +1s, no -1s):
http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201409.mbox/%3CCAKiyyaH0u%2BVgL-1e8TCMRwnnKT88cMPfNo2kVup2ShUeS1rmCA%40mail.gmail.com%3E

The tag to be voted on is release-0.6.1-rc0 (commit 0d3f3a1):
https://git-wip-us.apache.org/repos/asf?p=incubator-flink.git;a=commit;h=0d3f3a172f98837db039f4ac539c5630e294580c

The release artifacts to be voted on can be found at:
http://people.apache.org/~uce/flink-0.6.1-incubating-rc0/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/uce.asc

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapacheflink-1013/


Please vote on releasing this package as Apache Flink 0.6.1-incubating.

The vote will be open for at least 72 hours until:

Wednesday, September 19, 7:00 am (PDT, UTC-7) or 4:00 pm (CEST, UTC+2)
respectively.

[ ] +1 Release this package as Apache Flink 0.6.1-incubating
[ ] -1 Do not release this package because ...

Thanks,

The Apache Flink Team



--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Optiq 0.9.0 (incubating)

[Alan Gates]

+1.  Checked the LICENSE, NOTICE, and DISCLAIMER files.  Checked the 
md5, sha, and asc signatures.  Built and ran the tests on my mac.


Alan.


Julian Hyde mailto:jul...@hydromatic.net
August 22, 2014 at 0:34
Hi all,

The Optiq community has voted on and approved a proposal to release 
Apache Optiq 0.9.0 (incubating). This would be the first release of 
the Apache Optiq project inside the Incubator.


Pursuant to the Releases section of the Incubation Policy and with the 
endorsement of two of our mentors we would now like to request the 
permission of the Incubator PMC to publish the release. The vote is 
open for 72 hours, or until the necessary number of votes (3 +1) is 
reached.


[ ] +1 Release this package as Apache Optiq 0.9.0 incubating
[ ] -1 Do not release this package because …

Apache Optiq PPMC


Proposal:
http://mail-archives.apache.org/mod_mbox/incubator-optiq-dev/201408.mbox/%3CEFDC92D3-2D7A-4D69-96D6-261781F47BA5%40hydromatic.net%3E

Vote result:
5 binding +1 votes
5 non-binding +1 votes
No -1 votes
http://mail-archives.apache.org/mod_mbox/incubator-optiq-dev/201408.mbox/%3C455640FD-8F46-4C15-A1F0-09D47B944100%40hydromatic.net%3E

Artifacts:
http://people.apache.org/~jhyde/optiq-0.9.0-incubating-rc2/


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



--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Flink 0.6-incubating

[Alan Gates]

Forwarding my +1 from the dev list as well.

Alan.

P.S. Sorry, sent this a while ago but Apache has decided I'm a spambot and
bounced it.


On Mon, Aug 18, 2014 at 1:12 PM, Robert Metzger rmetz...@apache.org wrote:

 Hi all,

 This is to call for a vote for releasing Flink 0.6-incubating. This is the
 first release of the Apache Flink project inside the Incubator.

 Vote on d...@flink.incubator.apache.org:

 http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201408.mbox/%3CCAGr9p8AQWYhH4m37Pwt217ngaqZXJvU1qi82otX0PvBqTH3A_Q%40mail.gmail.com%3E
 http://s.apache.org/aS1

 Vote result: (8 binding +1 votes, no -1's)

 http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201408.mbox/%3CCAGr9p8A44XhKMFQw_FvCwyvrv-eRH0pkeza%2BrSgYRCoVYf5ujw%40mail.gmail.com%3E

 The commit to be voted upon:
 *http://git-wip-us.apache.org/repos/asf/incubator-flink/commit/053f4c65
 http://git-wip-us.apache.org/repos/asf/incubator-flink/commit/053f4c65*

 The artifacts to be voted on are located here:
 *http://people.apache.org/~rmetzger/flink-0.6-incubating-rc7/
 http://people.apache.org/~rmetzger/flink-0.6-incubating-rc7/*

 The GPG key (D9839159) used to sign the release is available at:
 https://dist.apache.org/repos/dist/release/incubator/flink/KEYS

 A staged Maven repository is available for review at:
 *https://repository.apache.org/content/repositories/orgapacheflink-1011/
 https://repository.apache.org/content/repositories/orgapacheflink-1011/*

 Please vote on releasing this package as Apache Flink 0.6-incubating.

 The vote will be open for at least 72 hours.

 [ ] +1 Release this package as Apache Flink 0.6-incubating
 [ ] +0 no opinion
 [ ] -1 Do not release this package because ...

 Thanks,
 The Apache Flink Team


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Graduate Apache Tez from Apache Incubator to TLP

[Alan Gates]

+1.

Alan.


Hitesh Shah mailto:hit...@apache.org
June 30, 2014 at 9:16 PM
Hello folks

Tez entered incubation in February, 2013. Since then, we have made 
progress towards graduation[1]. The Tez community recently voted 
positively towards graduation[2] with 27 +1s.

Of the 27, there were 5 IPMC votes from our mentors:
- Alan Gates
- Arun C. Murthy
- Chris Mattman
- Chris Douglas
- Jakob Homan

Now, I would like to ask the IPMC to vote for the graduation of Apache 
Tez.


Please VOTE to indicate if Apache Tez is ready to graduate as a Top 
Level Project. The board resolution is included below.


[ ] +1 Graduate Apache Tez as a TLP
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Tez as a TLP because…

The vote will remain open for 72 hours.

thanks
— Hitesh Shah ( on behalf of Tez PPMC )

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccfc4fef8.16337a%25chris.a.mattm...@jpl.nasa.gov%3E
[2] 
http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccaoapips7pjs_6hinkwk0uv0hnnrydqcg639dpf9vojeuto9...@mail.gmail.com%3E


Board Resolution:
--
X. Establish the Apache Tez Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to fast and flexible large-scale data analysis
on clusters.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Tez Project, be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further

RESOLVED, that the Apache Tez Project be and hereby is
responsible for the creation and maintenance of software
related to efficient cluster management, resource isolation
and sharing across distributed applications; and be it further
RESOLVED, that the office of Vice President, Apache Tez be
and hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Apache Tez Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache Tez Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Tez Project:

* Alan Gates ga...@apache.org
* Arun C. Murthy acmur...@apache.org
* Ashutosh Chauhan hashut...@apache.org
* Bill Graham billgra...@apache.org
* Bikas Saha bi...@apache.org
* Chris Douglas cdoug...@apache.org
* Chris Mattmann mattm...@apache.org
* Daryn Sharp da...@apache.org
* Devaraj Das d...@apache.org
* Gopal Vijayaraghavan gop...@apache.org
* Gunther Hagleitner gunt...@apache.org
* Hitesh Shah hit...@apache.org
* Jitendra Pandey jiten...@apache.org
* Jason Lowe jl...@apache.org
* Jakob Homan jgho...@apache.org
* Julien Le Dem jul...@apache.org
* Kevin Wilfong kevinwilf...@apache.org
* Mike Liddell mlidd...@apache.org
* Mohammad Kamrul Islam kam...@apache.org
* Namit Jain na...@apache.org
* Nathan Roberts nrobe...@apache.org
* Owen O’Malley omal...@apache.org
* Rajesh Balamohan rbalamo...@apache.org
* Robert Evans bo...@apache.org
* Rohini Palaniswamy roh...@apache.org
* Siddharth Seth ss...@apache.org
* Tassapol Athiapinya tassap...@apache.org
* Thomas Graves tgra...@apache.org
* Tom White tomwh...@apache.org
* Vikram Dixit vik...@apache.org
* Vinod Kumar Vavilapalli vino...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hitesh Shah be
appointed to the office of Vice President, Apache Tez, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed; and be it further

RESOLVED, that the Apache Tez Project be and hereby is
tasked with the migration and rationalization of the Apache
Incubator Tez podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Tez podling encumbered upon the Apache Incubator
Project are hereafter discharged.
--

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



--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution

Setting up git for a new podling

[Alan Gates]

All of the instruction I could find on podling setup talked about setting up 
SVN.  Are there instructions anywhere on how to setup git if the repository has 
requested that instead?  

Alan.
-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Fwd: [VOTE][RESULT] New name for the Stratosphere project

[Alan Gates]

Begin forwarded message:

 From: Robert Metzger rmetz...@apache.org
 Subject: Re: [VOTE][RESULT] New name for the Stratosphere project
 Date: May 14, 2014 at 2:40:26 AM PDT
 To: d...@stratosphere.incubator.apache.org
 Reply-To: d...@stratosphere.incubator.apache.org
 
 Thanks everybody for voting. The vote has closed and we have a result.
 
 Since we have 10 binding votes, the quota for accepting a name is 6 = (10 /
 1+1)+1.
 
 Flink has got exactly 6 binding votes and is therefore the winner.
 
 If we include the non-binding votes Flink has got 9 votes (of 15). The
 quota for non-binding is 8.5 = (15 / 2) +1. So Flink is winning both
 votes.
 We also evaluated the vote if Apache Legal disagrees with Flink, then
 Sfera would win.
 You can find the raw OpenOffice sheet exported as HTML here:
 http://people.apache.org/~rmetzger/stratosphere_vote.html
 (Thanks Fabian for evaluating the vote!)
 
 
 -- Robert
 
 
 On Tue, May 13, 2014 at 12:40 AM, Ted Dunning ted.dunn...@gmail.com wrote:
 
 Here is my ordering (officially binding, but I would request it to be
 non-binding)
 
 Orca
 Luna
 Sonic
 Ozone
 Garuda
 Moana
 Luwak
 Sfera
 Flink
 Tuber
 Euno
 


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Question on Stratosphere infrastructure

[Alan Gates]

When the Stratosphere project was accepted into the incubator they said they 
intended to change their name quickly.  To avoid extra work for the infra team 
we set up only the dev and private list for the project.  The project has now 
voted to change it’s name to Flink (German for quick).  I have filed a podling 
name search, https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-49 

Should I now set up the rest of the infrastructure (commits list, JIRA, 
website) so that the podling can get going in earnest?  It seems to me that I 
should since the podling is now in the same place as any new podling.  It has a 
name it thinks is ok but needs to go through trademark clearance.  I wanted to 
see if others agreed before I proceed.

Alan.
-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Accept Optiq into the incubator

[Alan Gates]

 with the Apache Brand ===
 
 Optiq solves a real problem, as evidenced by its take-up by other projects.
 This proposal is not for the purpose of generating publicity. Rather, the
 primary benefits to joining Apache are those outlined in the Rationale
 section.
 
 == Documentation ==
 
 Additional documentation for Optiq may be found on its github site:
 
 * [[https://github.com/julianhyde/optiq/blob/master/README.md|Overview]]
 * [[
 https://github.com/julianhyde/optiq-csv/blob/master/TUTORIAL.md|Tutorial]]
 * [[https://github.com/julianhyde/optiq/blob/master/HOWTO.md|HOWTO]]
 * 
 [[https://github.com/julianhyde/optiq/blob/master/REFERENCE.md|Referenceguide]]
 
  Presentation 
 
 *[[
 https://github.com/julianhyde/share/blob/master/slides/optiq-richrelevance-2013.pdf?raw=true|
 SQL on Big Data using Optiq]]
 == Initial Source ==
 
 The initial code codebase resides in three projects, all hosted on github:
 
 * https://github.com/julianhyde/optiq
 * https://github.com/julianhyde/optiq-csv
 * https://github.com/julianhyde/linq4j
 
 === Source and Intellectual Property Submission Plan ===
 
 The initial codebase is already distributed under the Apache 2.0 License.
 The owners of the IP have indicated willingness to sign the SGA.
 
 === External Dependencies ===
 
 Optiq and Linq4j have the following external dependencies.
 
 * Java 1.6, 1.7 or 1.8
 * Apache Maven, Commons
 * JavaCC (BSD license)
 * Sqlline 1.1.6 (BSD license)
 * Junit 4.11 (EPL)
 * Janino (BSD license)
 * Guava (Apache 2.0 license)
 * Eigenbase-resgen, eigenbase-xom, eigenbase-properties (Apache 2.0
 license)
 
 Some of Optiq's adapters (optiq-csv, optiq-mongodb, optiq-spark,
 optiq-splunk) are currently developed alongside core Optiq, and have the
 following additional dependencies:
 
 * Open CSV 2.3 (Apache 2.0 license)
 * Apache Incubator Spark
 * Mongo Java driver (Apache 2.0 license)
 Upon acceptance to the incubator, we would begin a thorough analysis of all
 transitive dependencies to verify this information and introduce license
 checking into the build and release process by integrating with Apache Rat.
 
 === Cryptography ===
 
 Optiq will eventually support encryption on the wire. This is not one of
 the initial goals, and we do not expect Optiq to be a controlled export
 item due to the use of encryption.
 
 == Required Resources ==
 
 === Mailing Lists ===
 
 * priv...@optiq.incubator.apache.org
 * d...@optiq.incubator.apache.org (will be migrated from
 optiq-...@googlegroups.com)
 * comm...@optiq.incubator.apache.org
 
 === Source control ===
 
 The Optiq team would like to use git for source control, due to our current
 use of git/github. We request a writeable git repo git://
 git.apache.org/incubator-optiq, and mirroring to be set up to github
 through INFRA.
 
 === Issue Tracking ===
 
 Optiq currently uses the github issue tracking system associated with its
 github repo: https://github.com/julianhyde/optiq/issues. We will migrate to
 the Apache JIRA: http://issues.apache.org/jira/browse/OPTIQ.
 
 == Initial Committers ==
 
 * Julian Hyde (jhyde at apache dot org)
 * Jacques Nadeau (jacques at apache dot org)
 * James R. Taylor (jamestaylor at apache dot org)
 * Chris Wensel (cwensel at apache dot org)
 
 === Affiliations ===
 
 The initial committers are employees of Concurrent, Hortonworks, MapR and
 Salesforce.com.
 
 * Julian Hyde (Hortonworks)
 * Jacques Nadeau (MapR Technologies)
 * James R. Taylor (Salesforce.com)
 * Chris Wensel (Concurrent)
 
 == Sponsors ==
 
 === Champion ===
 
 * Ashutosh Chauhan (hashutosh at apache dot org)
 
 === Nominated Mentors ===
 
 * Ted Dunning (tdunning at apache dot org) - Chief Application Architect
 at MapR Technologies; committer for Lucene, Mahout and ZooKeeper.
 * Alan Gates (gates at apache dot org) - Architect at Hortonworks;
 committer for Pig, Hive and others.
 * Steven Noels (stevenn at apache dot org) - Chief Technical Officer at
 NGDATA; committer for Cocoon and Forrest, mentor for Phoenix.
 
 === Sponsoring Entity ===
 
 The Apache Incubator.


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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