[VOTE] Release Apache Airflow 1.8.0 (incubating)

[Bolke de Bruin]

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 will rename release candidate 4 to final.

Airflow is a platform to programmatically author, schedule and monitor 
workflows. Use airflow to author workflows as directed acyclic graphs (DAGs) of 
tasks. The airflow scheduler executes your tasks on an array of workers while 
following the specified dependencies. Rich command line utilities make 
performing complex surgeries on DAGs a snap. The rich user interface makes it 
easy to visualize pipelines running in production, monitor progress, and 
troubleshoot issues when needed. When workflows are defined as code, they 
become more maintainable, versionable, testable, and collaborative.

The Apache Airflow-1.8.0-incubating release candidate is now available with the 
following artefacts for a project vote:

* [VOTE] Thread:*
http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201702.mbox/%3cd360d9be-c358-42a1-9188-6c92c31a2...@gmail.com%3e
 


*[RESULT][VOTE] Thread:*
http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201702.mbox/%3c0c96110d-2074-468a-bcac-a7feee331...@gmail.com%3e
 


*The release candidate(s) to be voted on is available at:*
https://dist.apache.org/repos/dist/dev/incubator/airflow/ 
 or 
https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc4+apache.incubating.tar.gz
 


*Git branch*
https://github.com/apache/incubator-airflow/tree/v1-8-stable 
 or 
https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-stable
 


PGP signature
https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc4+apache.incubating.tar.gz.asc
 


MD5/SHA Hashes:
https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc4+apache.incubating.tar.gz.md5
 

https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc4+apache.incubating.tar.gz.sha
 


*Keys to verify the signature of the release artifacts are available at:*
https://dist.apache.org/repos/dist/release/incubator/airflow/ 


* RAT License checks*

RAT is executed as part of the CI process (e.g. 
https://travis-ci.org/apache/incubator-airflow/builds/203106493 
) but can also 
be run manually by issuing “sh scripts/ci/check-license.sh” from the top level.

Source code is always included, i.e. there is no binary release. Compilation 
and installation will happen by standard Python practices, e.g. pip install <> 
or python setup.py install.

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

Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).

[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)


*Here is my +1 (non-binding)*

Cheers,
Bolke

Adding committers to a PPMC

[Henri Yandell]

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

[Marvin Humphrey]

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 is not
> actually changing).
>
> Is that not correct?

Correct, and well said!

When we assert that an Apache release package is available under the
ALv2 even though it bundles BSD-2-clause licensed code (as is the case
with MADlib), we are suggesting that the ALv2 "subsumes" the
BSD-2-clause license -- that fulfilling all the requirements of the
ALv2 suffices to fulfill all the requirements of the BSD-2-clause
license.

This is sometimes called "sublicensing", and it only works in one
direction: a license with more restrictions can subsume one with
fewer, but not the other way around.

In contrast, "relicensing" is usually taken to mean the original
copyright holder granting an *additional* license of any type. For
example, if you're the copyright holder, you can take something which
is available only under a proprietary license and make it available
under an open source license.  Or you could take something available
under the GPL and make it available under the ALv2.

(Of course the difficulty of "relicensing" in the context of open
source is that there may be many copyright holders who need to
participate in a relicensing effort -- and if you can't get them all
on board, you might have to strip out and replace code that couldn't
be relicensed.)

For more information on combining software under multiple open source
licenses, I like this article by Luis Villa:

   https://opensource.com/law/11/9/mpl-20-copyleft-and-license-compatibility

This is outdated but still a good read:

   http://www.catb.org/esr/Licensing-HOWTO.html#compatibility

Marvin Humphrey

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

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

[charlie (JIRA)]

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: LogoSubmission
Reporter: charlie
 Attachments: apache cmyk.png, apache rgb.png

designer: charlie bartlett
h...@charlieinblue.com

This seedling logo represents the potential for growth. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[ANNOUNCE] Release Apache RocketMQ 4.0.0 (incubating)

[yukon]

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:

https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/
or
https://dist.apache.org/repos/dist/release/incubator/rocketmq/4.0.0-incubating/

The release notes can be found here:

http://rocketmq.incubator.apache.org/release_notes/release-notes-4.0.0-incubating/

Thanks,
The Apache RocketMQ Team

— DISCLAIMER Apache RocketMQ is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
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: Voting now open for new Incubator Logo!

[Liang Chen]

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.

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

Voting now open for new Incubator Logo!

[John D. Ament]

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 vote.  After the community
vote, a selection committee will pull together these votes and other
factors to make a decision on the final new logo.

The voting closes in a week, 2/27 at midnight (11:59 pm).

Here's a link to the Google Form:
https://docs.google.com/forms/d/e/1FAIpQLSdJ5tud_4DtZjUAPvKDOtW21YxhitUcWRSqBZkBdWu8F5j-QQ/viewform

Please feel free to reach out with any questions.

John

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

[James Taylor]

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 Mon, Feb 20, 2017 at 3:21 PM Poorna Chandra  wrote:

> 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 fixing TEPHRA-223.
>
> Thanks,
> Poorna.
>
>
>
> On Mon, Feb 20, 2017 at 2:37 PM, James Taylor 
> wrote:
>
> > 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, 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 <
> go...@apache.org>
> > > > 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 of Apache Tephra-0.11.0-incubating [rc1]

[Poorna Chandra]

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 fixing TEPHRA-223.

Thanks,
Poorna.



On Mon, Feb 20, 2017 at 2:37 PM, James Taylor 
wrote:

> 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, 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 of Apache Tephra-0.11.0-incubating [rc1]

[James Taylor]

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, 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: Podling Graduation Rally

[Mike Jumper]

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, "John D. Ament"  wrote:

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

On Sun, Feb 19, 2017 at 11:19 PM Mike Jumper 
wrote:

> On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:
>
> ...
> CatA licenses are CatA because they allow modifications on source and
> re-license...
>
>
> sublicense*
>
> - Mike
>

Re: Podling Graduation Rally

[John D. Ament]

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

On Sun, Feb 19, 2017 at 11:19 PM Mike Jumper 
wrote:

> On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:
>
> ...
> CatA licenses are CatA because they allow modifications on source and
> re-license...
>
>
> sublicense*
>
> - Mike
>

Re: Podling Graduation Rally

[Roman Shaposhnik]

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 licensed source and
>> > modifies it (enough to claim copyright on the modifications) we
>> re-license
>> > to ALv2, but leaves the original BSD headers (if any) in the source.
>> >
>> > CatA licenses are CatA because they allow modifications on source and
>> > re-license...
>>
>> Correct. Which seems to make Roy's proposal a superset of what you're
>> talking
>> about. Now, while we can debate whether we can accomplish something similar
>> to what he was suggesting by some other means -- I'd rather vote for
>> simplicity
>> and go ahead with this:
>>
>> https://issues.apache.org/jira/browse/LEGAL-293?focusedCommentId=15873943=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15873943
>>
>> At this point -- I just need to see if there's anybody who's strongly
>> opposed this
>> approach.
>>
>
> Doing what you've outlined was my original request, so I have no qualms.
> It had seemed to me that the preference was to not relicense.  But I am
> glad we are relicensing.

No we are not. See Mike's reply above.

Thanks,
Roman.

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