Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[Gunther Hagleitner]

+1

Thanks,
Gunther.


On Sun, Feb 23, 2014 at 7:00 PM, Lianhui Wang wrote:

> +1.
>
>
> 2014-02-24 8:25 GMT+08:00 Bikas Saha :
>
> > +1.
> >
> >
> >
> > -Original Message-
> > From: Hitesh Shah [mailto:hit...@apache.org]
> > Sent: Sunday, February 23, 2014 11:31 AM
> > To: d...@tez.incubator.apache.org; general@incubator.apache.org
> > Subject: [VOTE] Release Apache Tez-0.3.0-incubating RC0
> >
> > Hello folks,
> >
> > I have created a tez-0.3.0-incubating release candidate (rc0). This is
> the
> > second release for Tez.
> >
> > GIT source tag:
> >
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez
> > .git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
> > Staging site:
> >
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
> > Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetez-1002
> >
> > PGP release keys:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> > KEYS file also available at
> > https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
> >
> > One can look into the issues fixed in this release at:
> > https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look
> > at the CHANGES.txt in the release tarball.
> >
> > Vote will be open for at least 72 hours ( until the required number of
> > IPMC votes are obtained ).
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > For folks not familiar with vetting a release, please refer to
> > http://incubator.apache.org/guides/releasemanagement.html#check-list
> >
> > thanks
> > -- Hitesh
> >
> > --
> > 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.
> >
>
>
>
> --
> thanks
>
> 王联辉(Lianhui Wang)
> blog; http://blog.csdn.net/lance_123
> 兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
>

-- 
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 Tez-0.3.0-incubating RC0

[Lianhui Wang]

+1.


2014-02-24 8:25 GMT+08:00 Bikas Saha :

> +1.
>
>
>
> -Original Message-
> From: Hitesh Shah [mailto:hit...@apache.org]
> Sent: Sunday, February 23, 2014 11:31 AM
> To: d...@tez.incubator.apache.org; general@incubator.apache.org
> Subject: [VOTE] Release Apache Tez-0.3.0-incubating RC0
>
> Hello folks,
>
> I have created a tez-0.3.0-incubating release candidate (rc0). This is the
> second release for Tez.
>
> GIT source tag:
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez
> .git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
> Staging site:
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
> Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetez-1002
>
> PGP release keys:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>
> One can look into the issues fixed in this release at:
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look
> at the CHANGES.txt in the release tarball.
>
> Vote will be open for at least 72 hours ( until the required number of
> IPMC votes are obtained ).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For folks not familiar with vetting a release, please refer to
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> thanks
> -- Hitesh
>
> --
> 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.
>



-- 
thanks

王联辉(Lianhui Wang)
blog; http://blog.csdn.net/lance_123
兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等

RE: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[Bikas Saha]

+1.



-Original Message-
From: Hitesh Shah [mailto:hit...@apache.org]
Sent: Sunday, February 23, 2014 11:31 AM
To: d...@tez.incubator.apache.org; general@incubator.apache.org
Subject: [VOTE] Release Apache Tez-0.3.0-incubating RC0

Hello folks,

I have created a tez-0.3.0-incubating release candidate (rc0). This is the
second release for Tez.

GIT source tag:
https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez
.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
Staging site:
https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetez-1002

PGP release keys:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
KEYS file also available at
https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

One can look into the issues fixed in this release at:
https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look
at the CHANGES.txt in the release tarball.

Vote will be open for at least 72 hours ( until the required number of
IPMC votes are obtained ).

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

For folks not familiar with vetting a release, please refer to
http://incubator.apache.org/guides/releasemanagement.html#check-list

thanks
-- Hitesh

-- 
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: Change of IPMC Chair

[Bertrand Delacretaz]

On Tue, Feb 4, 2014 at 3:02 AM, Marvin Humphrey  wrote:
> ...Congratulations to Roman Shaposhnik!  The Incubator PMC has voted to 
> recommend
> Roman as our next Chair in a resolution to the Board next week

FWIW, the corresponding resolution was passed by the ASF board last
week, so Roman as Incubator PMC chair is now effective - congrats and
thanks for accepting the job!

-Bertrand

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

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[sebb]

On 23 February 2014 19:31, Hitesh Shah  wrote:
> Hello folks,
>
> I have created a tez-0.3.0-incubating release candidate (rc0). This is the 
> second release for Tez.
>
> GIT source tag: 
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
> Staging site: 
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
> Nexus Staging URL: 
> https://repository.apache.org/content/repositories/orgapachetez-1002
>
> PGP release keys: 
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at 
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

Very good set of links.
Provides everything needed for reviewers to check the release contents.
Ideally the GIT hash should also be included, as tags are not immutable.
And for the mail archives it would be useful to include the SVN
revision for the dist/dev/ tag.

One minor point - the NOTICE file still says 2013; that should be
updated for the next release (assuming substantive changes have been
made in 2014)

> One can look into the issues fixed in this release at: 
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at 
> the CHANGES.txt in the release tarball.
>
> Vote will be open for at least 72 hours ( until the required number of IPMC 
> votes are obtained ).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For folks not familiar with vetting a release, please refer to 
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> thanks
> -- Hitesh
> -
> 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 Allura 1.1.0 incubating

[Henry Saputra]

NOTICE and LICENSE looks good.
Hash and Sig files are good.

+1 (binding)



- Henry

On Wed, Feb 12, 2014 at 5:06 PM, Dave Brondsema  wrote:
> Hi everyone,
>
> This is a call for a vote on Apache Allura 1.1.0 incubating. This will be our
> second release in the incubator.  Allura is forge software for the development
> of software projects, including source control systems, issue tracking,
> discussion, wiki, and other software project management tools.
>
> A vote was held on developer mailing list and it passed with 7 +1's, and no
> -1's or +0's.  1 vote was from an IPMC member (me).
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F15D4C.7060906%40brondsema.net%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52FBA8A9.502%40brondsema.net%3E
>
> Source tarball, signature and checksums are available at:
>   https://dist.apache.org/repos/dist/dev/incubator/allura/
>
> Checksums:
>   MD5:ea72b33323dc8c85ad26d08de4bbc534
>   SHA1:   170729db7c7b26fc3244293bc0a37989121d3973
>   SHA512:
> 24b65e731d2ec5df33ab4959b0edd72ec5fee58ae5ce704b10ef45ecc07259357a645d4989935423a6be7d4f1add8b2512578b9b2133ac5059f6d3c6d7235934
>
> The KEYS file can be found at:
>   http://www.apache.org/dist/incubator/allura/KEYS
>
> The release has been signed with key (9BB3CE70):
>   http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x56F0526F9BB3CE70
>
> Source corresponding to this release can be found at:
>   Commit: a2bc6726d63298638bacf4d02e697e92aaee0bf4
>   Tag:asf_release_1.1.0
>   Browse:
> https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.1.0
>
> The RAT report is available at:
>   https://sourceforge.net/p/allura/pastebin/52f15c143e5e833783530b74
>
> Vote will be open for at least 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Thanks!
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>   <><
>
> -
> 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 Phoenix 2.2.3 incubating

[Andrew Purtell]

Hi Sebb,

On Sat, Feb 22, 2014 at 2:19 AM, sebb  wrote:

> I've had a quick look at the (sole) archive, and it contains both
> source and compiled jars.
> Although it is OK to release convenience binaries, there must be a
> source only release, as that is the ASF mission - to release open
> source.
>

The "what must every release contain" doc says:

Every ASF release *must* contain a source package, which must be sufficient
for a user to build and test the release provided they have access to the
appropriate platform and tools. The source package must be cryptographically
signed  by the Release
Manager with a detached signature; and that package together with its
signature must be tested prior to voting +1 for release.


We can mentor the podling to produce a separate source only tarball, but
this might be a point of confusion, because the candidate tarball here
conforms to the above language, I have personally built and tested this
release from the properly signed tarball. It is a source tarball also
containing compiled binaries.


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

I'll cancel this vote and start a vote on a new RC shortly. There was a
pretty serious bug that was found in this one anyway.

Is it best practice to have a separate source-only tar bar and not include
the source in the binary tar ball? Or should it be included in both?

Thanks,
James


On Mon, Feb 24, 2014 at 10:11 AM, Andrew Purtell wrote:

> Hi Sebb,
>
> On Sat, Feb 22, 2014 at 2:19 AM, sebb  wrote:
>
> > I've had a quick look at the (sole) archive, and it contains both
> > source and compiled jars.
> > Although it is OK to release convenience binaries, there must be a
> > source only release, as that is the ASF mission - to release open
> > source.
> >
>
> The "what must every release contain" doc says:
>
> Every ASF release *must* contain a source package, which must be sufficient
> for a user to build and test the release provided they have access to the
> appropriate platform and tools. The source package must be
> cryptographically
> signed  by the Release
> Manager with a detached signature; and that package together with its
> signature must be tested prior to voting +1 for release.
>
>
> We can mentor the podling to produce a separate source only tarball, but
> this might be a point of confusion, because the candidate tarball here
> conforms to the above language, I have personally built and tested this
> release from the properly signed tarball. It is a source tarball also
> containing compiled binaries.
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[Henry Saputra]

Hi Andrew,

Are you saying it is ok to contain compiled executed binaries if they
were signed?

There had been long discussion in general@ list about what should be
contained in release artifacts (with 0.8.1 Spark release) and I
believe the conclusion was to avoid executable binaries in the source
release artifacts.

- Henry

On Mon, Feb 24, 2014 at 10:11 AM, Andrew Purtell  wrote:
> Hi Sebb,
>
> On Sat, Feb 22, 2014 at 2:19 AM, sebb  wrote:
>
>> I've had a quick look at the (sole) archive, and it contains both
>> source and compiled jars.
>> Although it is OK to release convenience binaries, there must be a
>> source only release, as that is the ASF mission - to release open
>> source.
>>
>
> The "what must every release contain" doc says:
>
> Every ASF release *must* contain a source package, which must be sufficient
> for a user to build and test the release provided they have access to the
> appropriate platform and tools. The source package must be cryptographically
> signed  by the Release
> Manager with a detached signature; and that package together with its
> signature must be tested prior to voting +1 for release.
>
>
> We can mentor the podling to produce a separate source only tarball, but
> this might be a point of confusion, because the candidate tarball here
> conforms to the above language, I have personally built and tested this
> release from the properly signed tarball. It is a source tarball also
> containing compiled binaries.
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

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

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[Andrew Purtell]

On Mon, Feb 24, 2014 at 10:20 AM, Henry Saputra wrote:

> Are you saying it is ok to contain compiled executed binaries if they
> were signed?
>

I did not take a position on that.

The how-to-release documentation perhaps has more room for interpretation
than is desirable.

There had been long discussion in general@ list about what should be contained
> in release artifacts (with 0.8.1 Spark release) and I believe the
> conclusion was to avoid executable binaries in the source release
> artifacts.
>

I missed this discussion. Probably this conclusion just hasn't surfaced
into documentation yet.

-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[sebb]

On 24 February 2014 18:25, Andrew Purtell  wrote:
> On Mon, Feb 24, 2014 at 10:20 AM, Henry Saputra 
> wrote:
>
>> Are you saying it is ok to contain compiled executed binaries if they
>> were signed?
>>
>
> I did not take a position on that.
>
> The how-to-release documentation perhaps has more room for interpretation
> than is desirable.
>
> There had been long discussion in general@ list about what should be contained
>> in release artifacts (with 0.8.1 Spark release) and I believe the
>> conclusion was to avoid executable binaries in the source release
>> artifacts.
>>
>
> I missed this discussion. Probably this conclusion just hasn't surfaced
> into documentation yet.

I think it is implied here

http://www.apache.org/dev/release.html#what (last para)

but I agree it should be make clearer elsewhere.

> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

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

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[Hitesh Shah]

Thanks for the review, Sebb. 

NOTICE file updated in trunk for the next release. I also made a change to our 
how-to-release documentation to ensure that the git hash and svn revisions are 
sent out in future votes.

thanks
-- Hitesh

On Feb 24, 2014, at 4:25 AM, sebb wrote:

> On 23 February 2014 19:31, Hitesh Shah  wrote:
>> Hello folks,
>> 
>> I have created a tez-0.3.0-incubating release candidate (rc0). This is the 
>> second release for Tez.
>> 
>> GIT source tag: 
>> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
>> Staging site: 
>> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
>> Nexus Staging URL: 
>> https://repository.apache.org/content/repositories/orgapachetez-1002
>> 
>> PGP release keys: 
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
>> KEYS file also available at 
>> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
> 
> Very good set of links.
> Provides everything needed for reviewers to check the release contents.
> Ideally the GIT hash should also be included, as tags are not immutable.
> And for the mail archives it would be useful to include the SVN
> revision for the dist/dev/ tag.
> 
> One minor point - the NOTICE file still says 2013; that should be
> updated for the next release (assuming substantive changes have been
> made in 2014)
> 
>> One can look into the issues fixed in this release at: 
>> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at 
>> the CHANGES.txt in the release tarball.
>> 
>> Vote will be open for at least 72 hours ( until the required number of IPMC 
>> votes are obtained ).
>> 
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>> 
>> For folks not familiar with vetting a release, please refer to 
>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>> 
>> thanks
>> -- Hitesh
>> -
>> 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

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

[David Nalley]

Yep - +1 (binding)

On Mon, Feb 24, 2014 at 1:17 AM, Mattmann, Chris A (3980)
 wrote:
> Awesome, thanks David, so is that your +1 for graduation?
>
> Cheers,
> Chris
>
>
>
>
> -Original Message-
> From: David Nalley 
> Reply-To: "general@incubator.apache.org" 
> Date: Sunday, February 23, 2014 10:15 PM
> To: "general@incubator.apache.org" 
> Cc: "d...@tajo.incubator.apache.org" 
> Subject: Re: [VOTE] Graduation of Apache Tajo from the Incubator
>
>>On Sun, Feb 23, 2014 at 2:02 AM, Hyunsik Choi  wrote:
>>> Hi David,
>>>
>>> Thank you for your checking.
>>> We updated the Tajo website according to the checklist.
>>> http://tajo.incubator.apache.org/
>>>
>>> Please check the site. If there are still missing things, please teach
>>>me.
>>>
>>> Best regards,
>>> Hyunsik Choi
>>>
>>
>>Thanks for the fast fixes, Hyunsik. Looks good to me.
>>
>>--David
>>
>>-
>>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

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

[Mattmann, Chris A (3980)]

Thanks David!





-Original Message-
From: David Nalley 
Reply-To: "general@incubator.apache.org" 
Date: Monday, February 24, 2014 1:20 PM
To: "general@incubator.apache.org" 
Cc: "d...@tajo.incubator.apache.org" 
Subject: Re: [VOTE] Graduation of Apache Tajo from the Incubator

>Yep - +1 (binding)
>
>On Mon, Feb 24, 2014 at 1:17 AM, Mattmann, Chris A (3980)
> wrote:
>> Awesome, thanks David, so is that your +1 for graduation?
>>
>> Cheers,
>> Chris
>>
>>
>>
>>
>> -Original Message-
>> From: David Nalley 
>> Reply-To: "general@incubator.apache.org" 
>> Date: Sunday, February 23, 2014 10:15 PM
>> To: "general@incubator.apache.org" 
>> Cc: "d...@tajo.incubator.apache.org" 
>> Subject: Re: [VOTE] Graduation of Apache Tajo from the Incubator
>>
>>>On Sun, Feb 23, 2014 at 2:02 AM, Hyunsik Choi 
>>>wrote:
 Hi David,

 Thank you for your checking.
 We updated the Tajo website according to the checklist.
 http://tajo.incubator.apache.org/

 Please check the site. If there are still missing things, please teach
me.

 Best regards,
 Hyunsik Choi

>>>
>>>Thanks for the fast fixes, Hyunsik. Looks good to me.
>>>
>>>--David
>>>
>>>-
>>>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
>


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

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

[Jake Farrell]

+1 (binding)

-Jake


On Fri, Feb 21, 2014 at 10:44 PM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hi Everyone,
>
> After a successful community VOTE [1] in which 4 IPMC members
> already VOTEd positively for graduation, I'm now calling an IPMC
> VOTE to graduate Tajo from the Incubator. Apache Tajo has
> seen successful Incubator releases, has added new contributors,
> has discussed their project on list and consistent with the
> Apache ways. There is a great momentum in the community and
> I am wholeheartedly recommending its graduation from the
> Incubator.
>
> Please VOTE below on the graduation of Apache Tajo from the
> Incubator. The graduation resolution is pasted below.
> I'll leave the VOTE open for at least 72 hours:
>
> [ ] +1 Graduate Apache Tajo from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Tajo from the Incubator because
>
> Here is my enthusiastic +1 for Tajo's graduation!
>
> Cheers,
> Chris
>
> [1] http://s.apache.org/sM
>
> ---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 low latency
>   queries, and extract, transform and load
> (ETL) operations for the Hadoop ecosystem.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>   (PMC), to be known as the "Apache Tajo Project" be and hereby is
>   established pursuant to Bylaws of the Foundation; and be it further
>
>   RESOLVED, that the Apache Tajo Project be and hereby is responsible
>   for the creation and maintenance of software
> related to low latency queries, and extract, transform and load
> (ETL) operations for the Hadoop ecosystem; and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Tajo", 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 Tajo Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
>   of the Apache Tajo 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 Tajo
>   Project:
>
> Alex Karasulu 
> Eli Reisman 
> Henry Saputra 
> Hyunsik Choi 
> Jakob Glen Homan 
> Chris Mattmann 
> Owen O'Malley 
> JaeHwa Jung 
> Jinho Kim 
> Jihoon Son 
> Keuntae Park 
> Roshan Sumbaly 
> Sangwook Kim 
> Yi Liu 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hyunsik Choi be appointed
> to the office of Vice President, Apache Tajo, 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 Tajo Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Tajo
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Tajo 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
>
>

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[Arun C Murthy]

+1 (binding)

Arun

On Feb 23, 2014, at 11:31 AM, Hitesh Shah  wrote:

> Hello folks,
> 
> I have created a tez-0.3.0-incubating release candidate (rc0). This is the 
> second release for Tez. 
> 
> GIT source tag: 
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
> Staging site: 
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
> Nexus Staging URL: 
> https://repository.apache.org/content/repositories/orgapachetez-1002
> 
> PGP release keys: 
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at 
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
> 
> One can look into the issues fixed in this release at: 
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at 
> the CHANGES.txt in the release tarball.
> 
> Vote will be open for at least 72 hours ( until the required number of IPMC 
> votes are obtained ).
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> For folks not familiar with vetting a release, please refer to 
> http://incubator.apache.org/guides/releasemanagement.html#check-list
> 
> thanks
> -- Hitesh
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



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

[CANCEL][VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

This vote is being cancelled because the RC did not include a source-only
tar ball. A new vote thread will be started with one that does.

Regards,
James

On Fri, Feb 21, 2014 at 5:12 PM, James Taylor wrote:

> Hello everyone,
>
> This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is
> a SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as
> a JDBC driver and enables querying and managing HBase tables using SQL.
> This will be our first release in the incubator.
>
> The RC is available for download at
> http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC2/ and
> is signed with my code signing key 5F5F3233.
>
> A vote was held on developer mailing list [1] and it passed with 4 +1's,
> and no
> -1's or +0's (2 votes were from IPMC members).
>
> Vote will be open for at least 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> James
>
> [1] Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E
>
>

[VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

Hello everyone,

This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as a
JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator.

The RC is available for download at
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/ and is
signed with my code signing key 5F5F3233. The source code may be found in
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating-src.tar.gzwhile
a convenience, pre-built binary may be found in
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating.tar.gz
.

GIT source tag:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3
GIT commit:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=5e7d071693b6ad4adb758b94d53808a75feeae26

Vote will be open for at least 72 hours:

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

Thanks!
James

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[Marvin Humphrey]

On Mon, Feb 24, 2014 at 10:25 AM, Andrew Purtell  wrote:
> The how-to-release documentation perhaps has more room for interpretation
> than is desirable.

FWIW, I've cleaned up some of the Incubator's Release Management guide and
though it's still messy overall, some chunks are ready for use IMO -- notably
the release checklist we hammered out last December.  The last item in the
checklist addresses this issue:

  http://incubator.apache.org/guides/releasemanagement.html#check-list

  Release consists of source code only, no binaries.

Clarifying the Foundation-level release documentation to emphasize that the
ASF only releases source is a Board action item which has been on the back
burner for some time.  If I finish cleaning up the Incubator docs and that
action item is still on the agenda I'll petition to have it assigned to me.

Taking a step back... My feeling about many of the ASF's policy docs is that
they would be clearer if they were formulated using imperatives
(SHOULD/MUST/etc.) rather than as FAQs.  Informational FAQs also have an
unfortunate tendency to harden into policy over time, leading to bloat.

> There had been long discussion in general@ list about what should be contained
>> in release artifacts (with 0.8.1 Spark release) and I believe the
>> conclusion was to avoid executable binaries in the source release
>> artifacts.
>
> I missed this discussion. Probably this conclusion just hasn't surfaced
> into documentation yet.

Here are some emails from Board member Roy Fielding on the subject:

http://s.apache.org/roy-binary-deps-0
http://s.apache.org/roy-binary-deps-1
http://s.apache.org/roy-binary-deps-2
http://s.apache.org/roy-binary-deps-3

Marvin Humphrey

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