[VOTE] Release Apache Airflow 1.8.0 (incubating)

Hello Incubator PMC’ers, The Apache Airflow community has voted and approved the proposal to release Apache Airflow 1.8.0 (incubating) based on 1.8.0 Release Candidate 4. We now kindly request the Incubator PMC members to review and vote on this incubator release. If the vote is successful we

Adding committers to a PPMC

When I look at https://whimsy.apache.org/roster/ppmc/mxnet - I only see the mentors for the project listed on the PPMC. Any idea what I need to modify to add the original committers from the proposal to the PPMC? Or do the mentors have to bootstrap and vote them all on? Thanks, Hen

Re: Podling Graduation Rally

On Mon, Feb 20, 2017 at 10:47 AM, Mike Jumper wrote: > AFAIK, only the copyright holder can relicense a copyrighted work, whereas > others may sublicense under compatible terms so long as the original > license grants that permission (ie: the license of the original work

[jira] [Created] (INCUBATOR-197) seedling logo

charlie created INCUBATOR-197: - Summary: seedling logo Key: INCUBATOR-197 URL: https://issues.apache.org/jira/browse/INCUBATOR-197 Project: Incubator Issue Type: Task Components:

[ANNOUNCE] Release Apache RocketMQ 4.0.0 (incubating)

Hi all, The Apache RocketMQ team would like to announce the release of Apache RocketMQ 4.0.0 (incubating). More details regarding Apache RocketMQ can be found at: http://rocketmq.incubator.apache.org/ The release artifacts can be downloaded here:

Re: Voting now open for new Incubator Logo!

Submitted my vote, thanks John. Regards Liang -- View this message in context: http://apache-incubator-general.996316.n3.nabble.com/Voting-now-open-for-new-Incubator-Logo-tp53887p53888.html Sent from the Apache Incubator - General mailing list archive at Nabble.com.

Voting now open for new Incubator Logo!

All, Thanks for everyone has submitted a proposed logo for the Incubator! The submissions are now over, and the voting can begin. We have a lot of great entrants. A full list can be found at https://issues.apache.org/jira/issues/?filter=12339142 Please note that this is a general community

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

IMHO, this bug is serious enough to be a showstopper. There's no workaround for it in depent projects such as Phoenix. How about we roll another RC with a fix today? Other non Apache projects don't need to wait until the release closes (or could even rely on non released bits). James On

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

Hey James, There are other projects that depend on the 0.11.0 release, and need it in the next couple of days. This bug can be worked around in the dependent projects. I suggest letting this release go through by marking TEPHRA-223 as a known issue. We can do a 0.11.1 release immediately after

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

Looks like a serious issue was found with TEPHRA-223, so switching my vote to -1. Hopefully we can get a quick fix with a new RC very soon. James On Fri, Feb 17, 2017 at 12:12 PM, Alan Gates wrote: > Forwarding my +1 from the dev list. > > Alan. > > > On Feb 17, 2017,

Re: Podling Graduation Rally

AFAIK, only the copyright holder can relicense a copyrighted work, whereas others may sublicense under compatible terms so long as the original license grants that permission (ie: the license of the original work is not actually changing). Is that not correct? - Mike On Feb 20, 2017 10:35 AM,

Re: Podling Graduation Rally

Mike, I'll point out that sublicense is probably not the right term. While both are Cat A, the BSD license is much less restrictive/offers less than the Apache license. Re-license is more accurate. Its still compatible with BSD, and removes any expectation that one is more/less than the other

Re: Podling Graduation Rally

On Mon, Feb 20, 2017 at 3:30 AM, John D. Ament wrote: > On Sun, Feb 19, 2017 at 11:09 PM Roman Shaposhnik > wrote: > >> On Sun, Feb 19, 2017 at 8:01 PM, Niclas Hedhman wrote: >> > I haven't followed this issue, but if we take BSD