date:20170316

Looks good.  Here's my +1

As I've said before, the package name doesn't block the release.  If you
can create a JIRA to track it, that would be great.

On Thu, Mar 16, 2017 at 9:02 PM Bolke de Bruin  wrote:

> Sure. Done
>
> On distribution naming and deprecation can we do this for the next release
> as it requires source code changes?
>
> - Bolke
>
>
> > On 16 Mar 2017, at 16:53, John D. Ament  wrote:
> >
> > Oh ok I see, thanks for the point.  Can you delete everything in
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/> that isn't the
> > release under vote?  I'll re-review at this point.
> >
> > For the distribution, is it possible for you to publish both
> apache-airflow
> > and just airflow, and somehow mark the old airflow release as deprecated?
> > either way won't block this release.
> >
> > John
> >
> > On Thu, Mar 16, 2017 at 7:45 PM Bolke de Bruin  > wrote:
> >
> >> Hey John,
> >>
> >> You seem to be unpacking BETA 1, instead of RELEASE CANDIDATE 5?
> >>
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> >>
> >> On #2, people will in general use “pip install ” which is a
> >> package manager.
> >>
> >> Cheers
> >> Bolke
> >>
> >>
> >>> On 16 Mar 2017, at 16:38, John D. Ament  wrote:
> >>>
> >>> Bolke,
> >>>
> >>> 1. Where do you see the DISCLAIMER?  It should be in the root, but I
> see
> >> it
> >>> no where in the archive.
> >>>
> >>> ~/Desktop/airflow-1.8.0b1+apache.incubating
> >>> ☺  ls
> >>>
> >>>
> >>> MANIFEST.in  PKG-INFO airflow  airflow.egg-info
> >>> setup.cfgsetup.py tests
> >>>
> >>> ~/Desktop/airflow-1.8.0b1+apache.incubating
> >>> ☺  find . -name "DISCLAIMER"
> >>>
> >>>
> >>>
> >>> ~/Desktop/airflow-1.8.0b1+apache.incubating
> >>> ☺
> >>>
> >>> 2. Since this is a source release, is the naming of the source release
> >>> critical for consumers?  Or do you leverage some kind of package
> manager
> >>> that understands it based on the archive name?  Either way, the blocker
> >> is
> >>> the DISCLAIMER, not this.
> >>>
> >>> John
> >>>
> >>> On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin  >> > wrote:
> >>>
>  Hi John,
> 
>  1. I checked the tar ball and it does contain the DISCLAIMER, is it
>  expected to be somewhere else?
> 
>  2. Is the naming a hard requirement and a blocker for this release?
> The
>  reason for naming it this way, it allows for upgrading from earlier
>  versions of Airflow that were managed outside Apache. Rebranding it as
> >> you
>  are suggesting would make it a lot harder for our users and not very
>  friendly to them.
> 
>  Cheers
>  Bolke
> 
> > On 16 Mar 2017, at 16:19, John D. Ament  > wrote:
> >
> > -1, release is missing necessary DISCLAIMER file.  Also to the point
> >> that
> > Jakob noted, the current artifact naming must be fixed (its a
> branding
> > issue from my POV).  It should be apache-airflow (or something like
> >> that)
> > not simply airflow.
> >
> > John
> >
> > On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  
>    bdbr...@gmail.com  >
> >> 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
> >> 5. 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:*
> >>
> >>
> 
> >>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Sure. Done 

On distribution naming and deprecation can we do this for the next release as 
it requires source code changes?

- Bolke


> On 16 Mar 2017, at 16:53, John D. Ament  wrote:
> 
> Oh ok I see, thanks for the point.  Can you delete everything in
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ 
>  that isn't the
> release under vote?  I'll re-review at this point.
> 
> For the distribution, is it possible for you to publish both apache-airflow
> and just airflow, and somehow mark the old airflow release as deprecated?
> either way won't block this release.
> 
> John
> 
> On Thu, Mar 16, 2017 at 7:45 PM Bolke de Bruin  > wrote:
> 
>> Hey John,
>> 
>> You seem to be unpacking BETA 1, instead of RELEASE CANDIDATE 5?
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
>> 
>> On #2, people will in general use “pip install ” which is a
>> package manager.
>> 
>> Cheers
>> Bolke
>> 
>> 
>>> On 16 Mar 2017, at 16:38, John D. Ament  wrote:
>>> 
>>> Bolke,
>>> 
>>> 1. Where do you see the DISCLAIMER?  It should be in the root, but I see
>> it
>>> no where in the archive.
>>> 
>>> ~/Desktop/airflow-1.8.0b1+apache.incubating
>>> ☺  ls
>>> 
>>> 
>>> MANIFEST.in  PKG-INFO airflow  airflow.egg-info
>>> setup.cfgsetup.py tests
>>> 
>>> ~/Desktop/airflow-1.8.0b1+apache.incubating
>>> ☺  find . -name "DISCLAIMER"
>>> 
>>> 
>>> 
>>> ~/Desktop/airflow-1.8.0b1+apache.incubating
>>> ☺
>>> 
>>> 2. Since this is a source release, is the naming of the source release
>>> critical for consumers?  Or do you leverage some kind of package manager
>>> that understands it based on the archive name?  Either way, the blocker
>> is
>>> the DISCLAIMER, not this.
>>> 
>>> John
>>> 
>>> On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin > > wrote:
>>> 
 Hi John,
 
 1. I checked the tar ball and it does contain the DISCLAIMER, is it
 expected to be somewhere else?
 
 2. Is the naming a hard requirement and a blocker for this release? The
 reason for naming it this way, it allows for upgrading from earlier
 versions of Airflow that were managed outside Apache. Rebranding it as
>> you
 are suggesting would make it a lot harder for our users and not very
 friendly to them.
 
 Cheers
 Bolke
 
> On 16 Mar 2017, at 16:19, John D. Ament  > wrote:
> 
> -1, release is missing necessary DISCLAIMER file.  Also to the point
>> that
> Jakob noted, the current artifact naming must be fixed (its a branding
> issue from my POV).  It should be apache-airflow (or something like
>> that)
> not simply airflow.
> 
> John
> 
> On Thu, Mar 16, 2017 at 12:40 PM 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
>> 5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
>>  
>> 
>> <
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
>>  
>>

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

2017-03-16 Thread Julian Hyde

And by the way, since this would be Quickstep’s first release under incubation, 
I gave them some leniency in my RC5 vote [1] on the dev list. I called out 2 
showstopper issues, which they fixed in RC6, and some other issues that they 
are going to fix in release 0.2.

(Being a mentor is very much being like a parent… good parents are lenient at 
times, but it’s hard for parents to agree on what to be lenient about.)

Julian

[1] 
https://lists.apache.org/thread.html/c31c994a092d5fa33d216b3919100f3d8392559eacab268f3ccb1455@%3Cdev.quickstep.apache.org%3E
 

 
> On Mar 16, 2017, at 4:42 PM, Josh Elser  wrote:
> 
> Given this is Quickstep's first release, yes, I think I could be persuaded to 
> make this a +1 given LEGAL-291 :)
> 
> I don't want to cause more confusion if you've already started re-rolling 
> things, Marc.
> 
> John D. Ament wrote:
>> So, knowing that some of the files are explained under LEGAL-291, would you
>> consider changing your vote?  While there are some changes to the LICENSE
>> file, its not a killer (since a user would see the correct licenses in the
>> source files).
>> 
>> I'd vote a +1 if there's a JIRA covering the fixes.  I would vote -1 if
>> that JIRA isn't fixed for the next release.
>> 
>> Here's a link to how to assemble the LICENSE contents, in case you need it:
>> http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 
>> John
>> 
>> On Thu, Mar 16, 2017 at 6:49 PM Josh Elser  wrote:
>> 
>>> 
>>> Marc Spehlmann wrote:
 Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating),
>>> everyone.
 With this I will close the vote.
 
 +1
 Julian (binding)
 Jignesh
 
 -1
 Josh (binding)
 
 As we received one -1 binding vote, we will not release rc6.
 
 ___
 
 The biggest issue seems to be our licensing checks.
 
 Now Fixed:
- third_party/src/cpplint/lint_everything.py
- ./parser/preprocessed/genfiles.sh
- ./query_execution/ForemanDistributed.cpp (not sure about the origin
>>> of
 this and the following three)
- ./query_execution/ForemanDistributed.hpp
- ./query_execution/PolicyEnforcerDistributed.cpp
- ./query_execution/PolicyEnforcerDistributed.hpp
- We checked the KEYS in the svn repo against the signed artifact and
>>> the
 sig is fine, it was just my info which was old on the people.apache site
>>> ->
 now updated.
- Our website has been updated to include the logo and reword "apache
 quickstep (incubating)".
 
 In progress:
 - We're reviewing what exactly goes in LICENSE/NOTICE files and will fix
 them for the next release.
>>> Feel free to ping if you'd like me to look over what you have put
>>> together before you spent time on the next RC. I can also provide some
>>> other examples of a LICENSE file which would look "similar".
>>> 
 Not Fixed:
- Julian turned us on to a previous issue with pre-processed parser
 files. It appears the content in /parser/preprocessed/ should be fine via
 discussion on https://issues.apache.org/jira/browse/LEGAL-291
>>> Thanks for this pointer! I thought something like this might have been
>>> the case (but was too lazy to parse it ;))
>>> 
>>> 
 Thank you,
 Marc
>>> - Josh
>>> 
>>> -
>>> 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] Publish Apache Edgent 1.1.0-incubating (RC1)

2017-03-16 Thread Katherine Marsden


+1


I checked the build and tests on Mac OSX for the source release. I hit 
one intermittent error in the testing that appears to be related to an 
external testing dependency and filed 
https://issues.apache.org/jira/browse/EDGENT-398



(accidentally sent my original response to the dev list)

Kathey


On 3/16/17 5:11 AM, Dale LaBossiere wrote:

Hey buddy, can you spare a VOTE?  :-)

Just another ping.  I appreciate that folks may have a lot of things on their 
plate at this time.

Thanks in advance for your help in getting this release out the door.
— Dale


On Mar 5, 2017, at 7:58 AM, Dale LaBossiere  wrote:

The Apache Edgent community approved a vote to release
Apache Edgent 1.1.0-incubating from RC1.

Per [1] we are requesting IPMC approval to publish the
release bundles on the distribution site [2].

This vote will be open for 120 hours (I’m on vacation :-)

- 1.1.0-incubating-RC1 vote results / thread [3]
- Git hash and tag for the release
 commit: 4744f56
 tag: 1.1.0-incubating-RC1
 link to RC1 source in the git repository [4]
- links to RC1 artifacts [5]

[ ]  +1 accept
[ ]  -1 reject (explanation required)

Thanks for your assistance in achieving this milestone!

[1] policy 
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
[2] distribution https://dist.apache.org/repos/dist/release/incubator/edgent/
[3] rc1 vote https://www.mail-archive.com/dev@edgent.apache.org/msg01477.html
[4] rc1 src repo 
https://github.com/apache/incubator-edgent/tree/1.1.0-incubating-RC1
[5] rc1 artifacts 
https://dist.apache.org/repos/dist/dev/incubator/edgent/1.1.0-incubating/rc1/



-
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: Donating freemarker-online as part of the FreeMarker project, how?

2017-03-16 Thread Daniel Dekany

Friday, March 17, 2017, 12:50:30 AM, John D. Ament wrote:

> The IPMC does not accept CCLAs, secretary does.  The CCLA is to grant
> ability for employees to contribute to apache project.  Since the project
> is already apache licensed, I don't think there's anything more you need
> done.

OK, I have already asked the donator to make a PR.

> Did you get a git repo created?

Yes (https://github.com/apache/incubator-freemarker-online-tester).

> John
>
> On Fri, Mar 10, 2017 at 1:27 PM Daniel Dekany  wrote:
>
>> To be clear, the ASF has confirmed receiving the CCLA, also I have
>> checked the contents of the CCLA (company name and persons match
>> reality). But because we are only a poddling project, I'm not sure if
>> we can now proceed with the pull request and merging, or we should
>> wait for confirmation from the IPMC.
>>
>>
>> Wednesday, March 8, 2017, 7:18:10 AM, Daniel Dekany wrote:
>>
>> > Yesterday the ASF has received the CCLA. Does the IPMC accept it, can
>> > we go ahead with the pull request?
>> >
>> > Thursday, February 23, 2017, 7:15:29 AM, Craig Russell wrote:
>> >
>> >> Hi Daniel,
>> >>
>> >>> On Feb 22, 2017, at 9:24 PM, Daniel Dekany 
>> wrote:
>> >>>
>> >>> Wednesday, February 22, 2017, 8:12:32 PM, Craig Russell wrote:
>> >>>
>>  Hi,
>> 
>>  Sounds like the easiest way to handle this is as you described.
>> >>>
>> >>> If we can do that, that's great! I will wait a few days to see if
>> >>> someone else has anything to add, then I will assume that the
>> >>> Incubator PMC has agreed and I will go ahead.
>> >>>
>>  Get a CCLA from Kenshoo with
>>  https://github.com/kenshoo/freemarker-online describing the code
>> being contributed
>>  Add any current Kenshoo employees
>>  Get an ICLA from non-Kenshoo folks
>> >>>
>> >>> I'm a bit confused regarding the last point above. We already got
>> >>> ICLA-s from the non-Kenshoo folks at the ASF, but they have
>> >>> contributed code to a non-ASF project back then. (Do we rather need an
>> >>> SGA from them maybe?)
>> >>
>> >> If you have ICLAs from all of the non-Kenshoo folks then nothing
>> >> else is needed from them. The ICLA is not project specific.
>> >>
>> >> Craig
>> >>>
>>  Create a git repo for the new content
>>  After we accept the CCLA, generate a pull request and take in the code
>>  Change package names
>>  Change license headers
>> 
>>  Craig
>> 
>> > On Feb 22, 2017, at 10:39 AM, Daniel Dekany 
>> wrote:
>> >
>> > Hello,
>> >
>> > This is related to the incubating FreeMarker project.
>> >
>> > A company called Kenshoo has developed a simple but handy online
>> > evaluator service for FreeMarker, some 3 years ago, and they are
>> still
>> > hosting it. Because they don't develop this service anymore, and
>> > because timely pull request merging and deployment seems to become an
>> > issue, we would like to bring the source code over to be part of the
>> > FreeMarker project. They are willing to donate the source code to the
>> > ASF.
>> >
>> > As of the more technical aspect of this, the FreeMarker project has
>> > multiple Git repos, one for each "product" (one product is the engine
>> > itself, another is the documentation/website generator Ant task, and
>> > yet another is the website content). These are separate products,
>> > because their versioning/releasing is independent. We would like to
>> > add one more such Git repo and product, for freemarker-online.
>> >
>> > We are trying to find out what's the most efficient yet legally
>> > acceptable way of doing this. Just as an example, after the repo was
>> > created and we add LICENSE and such, we could, technically, accept a
>> > pull request from Kenshoo if they sign a Corporate CLA. I know it's
>> an
>> > extreme approach as they contribute to an almost empty repo, OTOH we
>> > are talking about only 31 classes and some build files (~160 KB
>> source
>> > code). Anyway, how should we do it?
>> >
>> > The source code we want to bring over:
>> > https://github.com/kenshoo/freemarker-online
>> >
>> > Note that the 2 contributors from outside Kenshoo are also FreeMarker
>> > contributors, so we can get any papers needed from them (as there was
>> > no CLA signed at Kenshoo).
>> >
>> > --
>> > Thanks,
>> > Daniel Dekany
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> 
>>  Craig L Russell
>>  c...@apache.org
>> 
>> 
>> 
>>  -
>>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>

Re: [VOTE] Release Gossip (Incubating) version gossip-0.1.2-incubating (RC1)


Ugh, sorry for the duplicate votes folks...

Josh Elser wrote:

Fwd'ing my +1 (binding) from the ppmc

Edward Capriolo wrote:

I am pleased to call an IPMC vote for gossip-0.1.2-incubating.

The PPMC vote thread is here:

https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E


Additionally a description of the new features in the release is here:

https://lists.apache.org/thread.html/d244f03eba775c0de96bf527c67dce80e393c7ed614d43650cb23793@%3Cdev.gossip.apache.org%3E


Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thank you,
Edward



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

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Oh ok I see, thanks for the point.  Can you delete everything in
https://dist.apache.org/repos/dist/dev/incubator/airflow/ that isn't the
release under vote?  I'll re-review at this point.

For the distribution, is it possible for you to publish both apache-airflow
and just airflow, and somehow mark the old airflow release as deprecated?
 either way won't block this release.

John

On Thu, Mar 16, 2017 at 7:45 PM Bolke de Bruin  wrote:

> Hey John,
>
> You seem to be unpacking BETA 1, instead of RELEASE CANDIDATE 5?
>
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
>
> On #2, people will in general use “pip install ” which is a
> package manager.
>
> Cheers
> Bolke
>
>
> > On 16 Mar 2017, at 16:38, John D. Ament  wrote:
> >
> > Bolke,
> >
> > 1. Where do you see the DISCLAIMER?  It should be in the root, but I see
> it
> > no where in the archive.
> >
> > ~/Desktop/airflow-1.8.0b1+apache.incubating
> > ☺  ls
> >
> >
> > MANIFEST.in  PKG-INFO airflow  airflow.egg-info
> > setup.cfgsetup.py tests
> >
> > ~/Desktop/airflow-1.8.0b1+apache.incubating
> > ☺  find . -name "DISCLAIMER"
> >
> >
> >
> > ~/Desktop/airflow-1.8.0b1+apache.incubating
> > ☺
> >
> > 2. Since this is a source release, is the naming of the source release
> > critical for consumers?  Or do you leverage some kind of package manager
> > that understands it based on the archive name?  Either way, the blocker
> is
> > the DISCLAIMER, not this.
> >
> > John
> >
> > On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin  > wrote:
> >
> >> Hi John,
> >>
> >> 1. I checked the tar ball and it does contain the DISCLAIMER, is it
> >> expected to be somewhere else?
> >>
> >> 2. Is the naming a hard requirement and a blocker for this release? The
> >> reason for naming it this way, it allows for upgrading from earlier
> >> versions of Airflow that were managed outside Apache. Rebranding it as
> you
> >> are suggesting would make it a lot harder for our users and not very
> >> friendly to them.
> >>
> >> Cheers
> >> Bolke
> >>
> >>> On 16 Mar 2017, at 16:19, John D. Ament  wrote:
> >>>
> >>> -1, release is missing necessary DISCLAIMER file.  Also to the point
> that
> >>> Jakob noted, the current artifact naming must be fixed (its a branding
> >>> issue from my POV).  It should be apache-airflow (or something like
> that)
> >>> not simply airflow.
> >>>
> >>> John
> >>>
> >>> On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  >> >> wrote:
> >>>
>  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
>  5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
> >
>  <
> 
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> >
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> >
> >>>
> >
> 
>  *[RESULT][VOTE] Thread:*
> 
> 
> >>
>

Re: Donating freemarker-online as part of the FreeMarker project, how?

The IPMC does not accept CCLAs, secretary does.  The CCLA is to grant
ability for employees to contribute to apache project.  Since the project
is already apache licensed, I don't think there's anything more you need
done.  Did you get a git repo created?

John

On Fri, Mar 10, 2017 at 1:27 PM Daniel Dekany  wrote:

> To be clear, the ASF has confirmed receiving the CCLA, also I have
> checked the contents of the CCLA (company name and persons match
> reality). But because we are only a poddling project, I'm not sure if
> we can now proceed with the pull request and merging, or we should
> wait for confirmation from the IPMC.
>
>
> Wednesday, March 8, 2017, 7:18:10 AM, Daniel Dekany wrote:
>
> > Yesterday the ASF has received the CCLA. Does the IPMC accept it, can
> > we go ahead with the pull request?
> >
> > Thursday, February 23, 2017, 7:15:29 AM, Craig Russell wrote:
> >
> >> Hi Daniel,
> >>
> >>> On Feb 22, 2017, at 9:24 PM, Daniel Dekany 
> wrote:
> >>>
> >>> Wednesday, February 22, 2017, 8:12:32 PM, Craig Russell wrote:
> >>>
>  Hi,
> 
>  Sounds like the easiest way to handle this is as you described.
> >>>
> >>> If we can do that, that's great! I will wait a few days to see if
> >>> someone else has anything to add, then I will assume that the
> >>> Incubator PMC has agreed and I will go ahead.
> >>>
>  Get a CCLA from Kenshoo with
>  https://github.com/kenshoo/freemarker-online describing the code
> being contributed
>  Add any current Kenshoo employees
>  Get an ICLA from non-Kenshoo folks
> >>>
> >>> I'm a bit confused regarding the last point above. We already got
> >>> ICLA-s from the non-Kenshoo folks at the ASF, but they have
> >>> contributed code to a non-ASF project back then. (Do we rather need an
> >>> SGA from them maybe?)
> >>
> >> If you have ICLAs from all of the non-Kenshoo folks then nothing
> >> else is needed from them. The ICLA is not project specific.
> >>
> >> Craig
> >>>
>  Create a git repo for the new content
>  After we accept the CCLA, generate a pull request and take in the code
>  Change package names
>  Change license headers
> 
>  Craig
> 
> > On Feb 22, 2017, at 10:39 AM, Daniel Dekany 
> wrote:
> >
> > Hello,
> >
> > This is related to the incubating FreeMarker project.
> >
> > A company called Kenshoo has developed a simple but handy online
> > evaluator service for FreeMarker, some 3 years ago, and they are
> still
> > hosting it. Because they don't develop this service anymore, and
> > because timely pull request merging and deployment seems to become an
> > issue, we would like to bring the source code over to be part of the
> > FreeMarker project. They are willing to donate the source code to the
> > ASF.
> >
> > As of the more technical aspect of this, the FreeMarker project has
> > multiple Git repos, one for each "product" (one product is the engine
> > itself, another is the documentation/website generator Ant task, and
> > yet another is the website content). These are separate products,
> > because their versioning/releasing is independent. We would like to
> > add one more such Git repo and product, for freemarker-online.
> >
> > We are trying to find out what's the most efficient yet legally
> > acceptable way of doing this. Just as an example, after the repo was
> > created and we add LICENSE and such, we could, technically, accept a
> > pull request from Kenshoo if they sign a Corporate CLA. I know it's
> an
> > extreme approach as they contribute to an almost empty repo, OTOH we
> > are talking about only 31 classes and some build files (~160 KB
> source
> > code). Anyway, how should we do it?
> >
> > The source code we want to bring over:
> > https://github.com/kenshoo/freemarker-online
> >
> > Note that the 2 contributors from outside Kenshoo are also FreeMarker
> > contributors, so we can get any papers needed from them (as there was
> > no CLA signed at Kenshoo).
> >
> > --
> > Thanks,
> > Daniel Dekany
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> 
>  Craig L Russell
>  c...@apache.org
> 
> 
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> >>>
> >>> --
> >>> Thanks,
> >>> Daniel Dekany
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For

Re: [VOTE] Release Gossip (Incubating) version gossip-0.1.2-incubating (RC1)

+1 to release.

On Mon, Mar 13, 2017 at 4:03 PM Edward Capriolo 
wrote:

> I am pleased to call an IPMC vote for gossip-0.1.2-incubating.
>
> The PPMC vote thread is here:
>
>
> https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E
>
> Additionally a description of the new features in the release is here:
>
>
> https://lists.apache.org/thread.html/d244f03eba775c0de96bf527c67dce80e393c7ed614d43650cb23793@%3Cdev.gossip.apache.org%3E
>
> Release this package?
> [ ] +1 yes
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thank you,
> Edward
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Arthur Wiedmer

Hi John,

1. The release candidate is 1.8.0rc5, is there a particular naming
convention we should be using there?

I will let Bolke comment on 2., but usually the Python pip package manager
is sensitive to the naming of the archive, unfortunately.

Best,
Arthur.

On Thu, Mar 16, 2017 at 4:38 PM, John D. Ament 
wrote:

> Bolke,
>
> 1. Where do you see the DISCLAIMER?  It should be in the root, but I see it
> no where in the archive.
>
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺  ls
>
>
> MANIFEST.in  PKG-INFO airflow  airflow.egg-info
> setup.cfgsetup.py tests
>
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺  find . -name "DISCLAIMER"
>
>
>
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺
>
> 2. Since this is a source release, is the naming of the source release
> critical for consumers?  Or do you leverage some kind of package manager
> that understands it based on the archive name?  Either way, the blocker is
> the DISCLAIMER, not this.
>
> John
>
> On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin  wrote:
>
> > Hi John,
> >
> > 1. I checked the tar ball and it does contain the DISCLAIMER, is it
> > expected to be somewhere else?
> >
> > 2. Is the naming a hard requirement and a blocker for this release? The
> > reason for naming it this way, it allows for upgrading from earlier
> > versions of Airflow that were managed outside Apache. Rebranding it as
> you
> > are suggesting would make it a lot harder for our users and not very
> > friendly to them.
> >
> > Cheers
> > Bolke
> >
> > > On 16 Mar 2017, at 16:19, John D. Ament  wrote:
> > >
> > > -1, release is missing necessary DISCLAIMER file.  Also to the point
> that
> > > Jakob noted, the current artifact naming must be fixed (its a branding
> > > issue from my POV).  It should be apache-airflow (or something like
> that)
> > > not simply airflow.
> > >
> > > John
> > >
> > > On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  > > wrote:
> > >
> > >> 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
> > >> 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> 135caf930...@gmail.com%3e
> > >> <
> > >>
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3CB1833A3A-05FB-4112-B395-
> 135caf930...@gmail.com%3E
> > <
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3CB1833A3A-05FB-4112-B395-
> 135caf930...@gmail.com%3E
> > >
> > >>>
> > >>
> > >> *[RESULT][VOTE] Thread:*
> > >>
> > >>
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e
> > <
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e
> > >
> > >> <
> > >>
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e
> > <
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e
> > >
> > >>>
> > >>
> > >> *The release candidate(s) to be voted on is available at:*
> > >> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/> <
> > >> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/>> or
> > >>
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> airflow-1.8.0rc5+apache.incubating.tar.gz
> > <
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Hey John,

You seem to be unpacking BETA 1, instead of RELEASE CANDIDATE 5? 

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

On #2, people will in general use “pip install ” which is a package 
manager.

Cheers
Bolke


> On 16 Mar 2017, at 16:38, John D. Ament  wrote:
> 
> Bolke,
> 
> 1. Where do you see the DISCLAIMER?  It should be in the root, but I see it
> no where in the archive.
> 
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺  ls
> 
> 
> MANIFEST.in  PKG-INFO airflow  airflow.egg-info
> setup.cfgsetup.py tests
> 
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺  find . -name "DISCLAIMER"
> 
> 
> 
> ~/Desktop/airflow-1.8.0b1+apache.incubating
> ☺
> 
> 2. Since this is a source release, is the naming of the source release
> critical for consumers?  Or do you leverage some kind of package manager
> that understands it based on the archive name?  Either way, the blocker is
> the DISCLAIMER, not this.
> 
> John
> 
> On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin  > wrote:
> 
>> Hi John,
>> 
>> 1. I checked the tar ball and it does contain the DISCLAIMER, is it
>> expected to be somewhere else?
>> 
>> 2. Is the naming a hard requirement and a blocker for this release? The
>> reason for naming it this way, it allows for upgrading from earlier
>> versions of Airflow that were managed outside Apache. Rebranding it as you
>> are suggesting would make it a lot harder for our users and not very
>> friendly to them.
>> 
>> Cheers
>> Bolke
>> 
>>> On 16 Mar 2017, at 16:19, John D. Ament  wrote:
>>> 
>>> -1, release is missing necessary DISCLAIMER file.  Also to the point that
>>> Jakob noted, the current artifact naming must be fixed (its a branding
>>> issue from my POV).  It should be apache-airflow (or something like that)
>>> not simply airflow.
>>> 
>>> John
>>> 
>>> On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin > >> wrote:
>>> 
 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
 5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
>>  
>> 
 <
 
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
>>  
>> 
>> <
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
>>  
>> 
>>> 
> 
 
 *[RESULT][VOTE] Thread:*
 
 
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
>>  
>> 
>> <
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
>>  
>> 
>>> 
 <
 
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
>>  
>>

Re: [VOTE] Release Gossip (Incubating) version gossip-0.1.2-incubating (RC1)


Fwd'ing my +1 (binding) from the ppmc

Edward Capriolo wrote:

I am pleased to call an IPMC vote for gossip-0.1.2-incubating.

The PPMC vote thread is here:

https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E

Additionally a description of the new features in the release is here:

https://lists.apache.org/thread.html/d244f03eba775c0de96bf527c67dce80e393c7ed614d43650cb23793@%3Cdev.gossip.apache.org%3E

Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thank you,
Edward



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

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

Given this is Quickstep's first release, yes, I think I could be 
persuaded to make this a +1 given LEGAL-291 :)


I don't want to cause more confusion if you've already started 
re-rolling things, Marc.


John D. Ament wrote:

So, knowing that some of the files are explained under LEGAL-291, would you
consider changing your vote?  While there are some changes to the LICENSE
file, its not a killer (since a user would see the correct licenses in the
source files).

I'd vote a +1 if there's a JIRA covering the fixes.  I would vote -1 if
that JIRA isn't fixed for the next release.

Here's a link to how to assemble the LICENSE contents, in case you need it:
http://www.apache.org/dev/licensing-howto.html#permissive-deps

John

On Thu, Mar 16, 2017 at 6:49 PM Josh Elser  wrote:



Marc Spehlmann wrote:

Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating),

everyone.

With this I will close the vote.

+1
Julian (binding)
Jignesh

-1
Josh (binding)

As we received one -1 binding vote, we will not release rc6.

___

The biggest issue seems to be our licensing checks.

Now Fixed:
- third_party/src/cpplint/lint_everything.py
- ./parser/preprocessed/genfiles.sh
- ./query_execution/ForemanDistributed.cpp (not sure about the origin

of

this and the following three)
- ./query_execution/ForemanDistributed.hpp
- ./query_execution/PolicyEnforcerDistributed.cpp
- ./query_execution/PolicyEnforcerDistributed.hpp
- We checked the KEYS in the svn repo against the signed artifact and

the

sig is fine, it was just my info which was old on the people.apache site

->

now updated.
- Our website has been updated to include the logo and reword "apache
quickstep (incubating)".

In progress:
- We're reviewing what exactly goes in LICENSE/NOTICE files and will fix
them for the next release.

Feel free to ping if you'd like me to look over what you have put
together before you spent time on the next RC. I can also provide some
other examples of a LICENSE file which would look "similar".


Not Fixed:
- Julian turned us on to a previous issue with pre-processed parser
files. It appears the content in /parser/preprocessed/ should be fine via
discussion on https://issues.apache.org/jira/browse/LEGAL-291

Thanks for this pointer! I thought something like this might have been
the case (but was too lazy to parse it ;))



Thank you,
Marc

- Josh

-
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] Publish Apache Edgent 1.1.0-incubating (RC1)

+1 to cut the release, contents look good.

On Thu, Mar 16, 2017 at 8:11 AM Dale LaBossiere  wrote:

> Hey buddy, can you spare a VOTE?  :-)
>
> Just another ping.  I appreciate that folks may have a lot of things on
> their plate at this time.
>
> Thanks in advance for your help in getting this release out the door.
> — Dale
>
> > On Mar 5, 2017, at 7:58 AM, Dale LaBossiere  wrote:
> >
> > The Apache Edgent community approved a vote to release
> > Apache Edgent 1.1.0-incubating from RC1.
> >
> > Per [1] we are requesting IPMC approval to publish the
> > release bundles on the distribution site [2].
> >
> > This vote will be open for 120 hours (I’m on vacation :-)
> >
> > - 1.1.0-incubating-RC1 vote results / thread [3]
> > - Git hash and tag for the release
> >  commit: 4744f56
> >  tag: 1.1.0-incubating-RC1
> >  link to RC1 source in the git repository [4]
> > - links to RC1 artifacts [5]
> >
> > [ ]  +1 accept
> > [ ]  -1 reject (explanation required)
> >
> > Thanks for your assistance in achieving this milestone!
> >
> > [1] policy
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> > [2] distribution
> https://dist.apache.org/repos/dist/release/incubator/edgent/
> > [3] rc1 vote
> https://www.mail-archive.com/dev@edgent.apache.org/msg01477.html
> > [4] rc1 src repo
> https://github.com/apache/incubator-edgent/tree/1.1.0-incubating-RC1
> > [5] rc1 artifacts
> https://dist.apache.org/repos/dist/dev/incubator/edgent/1.1.0-incubating/rc1/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Bolke,

1. Where do you see the DISCLAIMER?  It should be in the root, but I see it
no where in the archive.

~/Desktop/airflow-1.8.0b1+apache.incubating
☺  ls


MANIFEST.in  PKG-INFO airflow  airflow.egg-info
setup.cfgsetup.py tests

~/Desktop/airflow-1.8.0b1+apache.incubating
☺  find . -name "DISCLAIMER"



~/Desktop/airflow-1.8.0b1+apache.incubating
☺

2. Since this is a source release, is the naming of the source release
critical for consumers?  Or do you leverage some kind of package manager
that understands it based on the archive name?  Either way, the blocker is
the DISCLAIMER, not this.

John

On Thu, Mar 16, 2017 at 7:32 PM Bolke de Bruin  wrote:

> Hi John,
>
> 1. I checked the tar ball and it does contain the DISCLAIMER, is it
> expected to be somewhere else?
>
> 2. Is the naming a hard requirement and a blocker for this release? The
> reason for naming it this way, it allows for upgrading from earlier
> versions of Airflow that were managed outside Apache. Rebranding it as you
> are suggesting would make it a lot harder for our users and not very
> friendly to them.
>
> Cheers
> Bolke
>
> > On 16 Mar 2017, at 16:19, John D. Ament  wrote:
> >
> > -1, release is missing necessary DISCLAIMER file.  Also to the point that
> > Jakob noted, the current artifact naming must be fixed (its a branding
> > issue from my POV).  It should be apache-airflow (or something like that)
> > not simply airflow.
> >
> > John
> >
> > On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  > wrote:
> >
> >> 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
> >> 5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> >
> >>>
> >>
> >> *[RESULT][VOTE] Thread:*
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> >
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> >
> >>>
> >>
> >> *The release candidate(s) to be voted on is available at:*
> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/> <
> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/>> or
> >>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> >
> >> <
> >>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> >
> >>>
> >>
> >> *Git branch*
> >> https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> https://github.com/apache/incubator-airflow/tree/v1-8-stable> <
> >> https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> https://github.com/apache/incubator-airflow/tree/v1-8-stable>> or
> >>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Hi John,

1. I checked the tar ball and it does contain the DISCLAIMER, is it expected to 
be somewhere else?

2. Is the naming a hard requirement and a blocker for this release? The reason 
for naming it this way, it allows for upgrading from earlier versions of 
Airflow that were managed outside Apache. Rebranding it as you are suggesting 
would make it a lot harder for our users and not very friendly to them.

Cheers
Bolke

> On 16 Mar 2017, at 16:19, John D. Ament  wrote:
> 
> -1, release is missing necessary DISCLAIMER file.  Also to the point that
> Jakob noted, the current artifact naming must be fixed (its a branding
> issue from my POV).  It should be apache-airflow (or something like that)
> not simply airflow.
> 
> John
> 
> On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  > wrote:
> 
>> 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
>> 5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
>> <
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
>>  
>> 
>>> 
>> 
>> *[RESULT][VOTE] Thread:*
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
>>  
>> 
>> <
>> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
>>  
>> 
>>> 
>> 
>> *The release candidate(s) to be voted on is available at:*
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/ 
>>  <
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/ 
>> > or
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
>>  
>> 
>> <
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
>>  
>> 
>>> 
>> 
>> *Git branch*
>> https://github.com/apache/incubator-airflow/tree/v1-8-stable 
>>  <
>> 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
>>  
>> 
>> <
>> 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
>>  
>> 
>>> 
>> 
>> *Git tag*
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2
>>  
>> 
>> <
>> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2
>>  
>>

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

Madhan,

In the future, when pointing to a release, please point to the directory,
not the individual artifacts.  The reason being, it could be hard to find
the related asc/md5/ etc files (even though you did include the direct
links a few lines down, its purely convention).  So I would recommend using
this link:
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/

I would like to see the standard disclaimer used in the future, is there a
reason to not use it?
http://incubator.apache.org/guides/branding.html#disclaimers

Other than that, the release contents look good.  So +1 from me.

John

On Sat, Mar 11, 2017 at 12:46 PM 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
>
>

Re: [VOTE] Release Apache Mynewt 1.0.0-incubating-rc1

+1 for the release, good luck!

On Mon, Mar 13, 2017 at 12:09 AM marko kiiskila  wrote:

> The Apache Mynewt Incubator PPMC has approved a proposal to release
> Apache Mynewt 1.0.0-incubating-rc1. We now kindly request that the
> Incubator PMC members review and vote on this incubator release.
>
> Apache Mynewt is a community-driven, permissively licensed open source
> initiative for constrained, embedded applications.  Mynewt provides a
> real-time operating system, flash file system, network stacks, and
> support utilities for real-world embedded systems.
>
> For full release notes, please visit the Apache Mynewt Wiki:
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes <
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes>
>
> [VOTE] thread:
>
> https://lists.apache.org/thread.html/030cd65553128847b6931b3e32e0536326036ce9f332feb988759f55@%3Cdev.mynewt.apache.org%3E
> <
> https://lists.apache.org/thread.html/030cd65553128847b6931b3e32e0536326036ce9f332feb988759f55@%3Cdev.mynewt.apache.org%3E
> >
>
> [RESULT][VOTE] thread:
>
> https://lists.apache.org/thread.html/e863e81c7b4af0981610775d541f2a51a6814e4523fd74e1a402341a@%3Cdev.mynewt.apache.org%3E
> <
> https://lists.apache.org/thread.html/e863e81c7b4af0981610775d541f2a51a6814e4523fd74e1a402341a@%3Cdev.mynewt.apache.org%3E
> >
>
> [DISCUSS] thread:
>
> https://lists.apache.org/thread.html/f2e3c8bc63a377dd628a2bdafb7b160868525a134f75d766d7244578@%3Cdev.mynewt.apache.org%3E
> <
> https://lists.apache.org/thread.html/f2e3c8bc63a377dd628a2bdafb7b160868525a134f75d766d7244578@%3Cdev.mynewt.apache.org%3E
> >
>
> This release candidate was tested as follows:
>  1. Manual execution of the Mynewt test plan:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
> <
> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
> >
> The test results can be found at:
> https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0+Test+Results
> 
>  2. The full unit test suite for this release was executed via "newt
> test all" with no failures.  This testing was performed on the
> following platforms:
>   * OS X 10.12.3
>   * Linux Ubuntu 14.04.4
>
> The release candidate to be voted on is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/
> <
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/
> >
>
> The commits under consideration are as follows:
> blinky:
>  repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky <
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky>
>  commit 15496854000a2b0cc9d19c05e069d18be313fa28
> core:
>  repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core <
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core>
>  commit 0db6321a75deda126943aa187842da6b977cd1c1
> newt:
>  repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt <
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt>
>  commit c42ebdce8c278a00fa8d68ed342c45cd22e44dfb
>
> In addition, the following newt convenience binaries are available:
>  linux:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-linux-1.0.0-incubating.tgz
> <
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-linux-1.0.0-incubating.tgz
> >
>  osx:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-osx-1.0.0-incubating.tgz
> <
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-osx-1.0.0-incubating.tgz
> >
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS>
>
> The vote is open for at least 72 hours and passes if a majority of at
> least three +1 PPMC votes are cast.
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because…
>
> —
> M

Re: [VOTE] Apache Slider (incubating) release 0.92.0-incubating

+1 release contents look on point.  Thanks for the simple one!

John

On Wed, Mar 15, 2017 at 7:15 PM Gour Saha  wrote:

> Hello,
>
> This is a call for a vote on the Apache Slider (incubating) release
> 0.92.0-incubating.
>
> This release candidate, 0.92.0-incubating-RC0 has successfully passed a
> vote for a release on the slider developer mailing list.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4E792AE.2693A%25gsaha%40hortonworks.com%3E
>
> Results:
>
> http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4EEB66E.26E31%25gsaha%40hortonworks.com%3E
>
> Source artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/slider/0.92.0-incubating-RC0
>
> Staged artifacts:
>   https://repository.apache.org/content/repositories/orgapacheslider-1017/
>
> Git source:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=c41b1c7051d02c02b0d78cab859c7e15d0af92c9
>
> Git commit SHA1: c41b1c7051d02c02b0d78cab859c7e15d0af92c9
>
> Issues fixed:
>   https://issues.apache.org/jira/browse/SLIDER/fixforversion/12339846/
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315422=12339846
>
> PGP key:
>
> http://pgp.mit.edu:11371/pks/lookup?op=vindex=gourks...@apache.org
>
> Please vote on releasing this package as Apache Slider 0.92.0-incubating:
>
> This vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> gourksaha on behalf of the Apache Slider (incubating) team
>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

-1, release is missing necessary DISCLAIMER file.  Also to the point that
Jakob noted, the current artifact naming must be fixed (its a branding
issue from my POV).  It should be apache-airflow (or something like that)
not simply airflow.

John

On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin  wrote:

> 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
> 5. 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/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3cb1833a3a-05fb-4112-b395-135caf930...@gmail.com%3E
> >
>
> *[RESULT][VOTE] Thread:*
>
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59bc8c2b-12e2-4de3-9555-b2273660a...@gmail.com%3e
> >
>
> *The release candidate(s) to be voted on is available at:*
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> >
>
> *Git branch*
> https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> 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
> <
> 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
> >
>
> *Git tag*
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2
> >
>
> PGP signature
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz.asc
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz.asc
> >
>
> MD5/SHA Hashes:
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz.md5
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz.md5
> >
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz.sha
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+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/ <
> 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 <
> 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

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

So, knowing that some of the files are explained under LEGAL-291, would you
consider changing your vote?  While there are some changes to the LICENSE
file, its not a killer (since a user would see the correct licenses in the
source files).

I'd vote a +1 if there's a JIRA covering the fixes.  I would vote -1 if
that JIRA isn't fixed for the next release.

Here's a link to how to assemble the LICENSE contents, in case you need it:
http://www.apache.org/dev/licensing-howto.html#permissive-deps

John

On Thu, Mar 16, 2017 at 6:49 PM Josh Elser  wrote:

>
>
> Marc Spehlmann wrote:
> > Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating),
> everyone.
> > With this I will close the vote.
> >
> > +1
> > Julian (binding)
> > Jignesh
> >
> > -1
> > Josh (binding)
> >
> > As we received one -1 binding vote, we will not release rc6.
> >
> > ___
> >
> > The biggest issue seems to be our licensing checks.
> >
> > Now Fixed:
> >- third_party/src/cpplint/lint_everything.py
> >- ./parser/preprocessed/genfiles.sh
> >- ./query_execution/ForemanDistributed.cpp (not sure about the origin
> of
> > this and the following three)
> >- ./query_execution/ForemanDistributed.hpp
> >- ./query_execution/PolicyEnforcerDistributed.cpp
> >- ./query_execution/PolicyEnforcerDistributed.hpp
> >- We checked the KEYS in the svn repo against the signed artifact and
> the
> > sig is fine, it was just my info which was old on the people.apache site
> ->
> > now updated.
> >- Our website has been updated to include the logo and reword "apache
> > quickstep (incubating)".
> >
> > In progress:
> > - We're reviewing what exactly goes in LICENSE/NOTICE files and will fix
> > them for the next release.
>
> Feel free to ping if you'd like me to look over what you have put
> together before you spent time on the next RC. I can also provide some
> other examples of a LICENSE file which would look "similar".
>
> > Not Fixed:
> >- Julian turned us on to a previous issue with pre-processed parser
> > files. It appears the content in /parser/preprocessed/ should be fine via
> > discussion on https://issues.apache.org/jira/browse/LEGAL-291
>
> Thanks for this pointer! I thought something like this might have been
> the case (but was too lazy to parse it ;))
>
>
> > Thank you,
> > Marc
>
> - Josh
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6




Marc Spehlmann wrote:

Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating), everyone.
With this I will close the vote.

+1
Julian (binding)
Jignesh

-1
Josh (binding)

As we received one -1 binding vote, we will not release rc6.

___

The biggest issue seems to be our licensing checks.

Now Fixed:
   - third_party/src/cpplint/lint_everything.py
   - ./parser/preprocessed/genfiles.sh
   - ./query_execution/ForemanDistributed.cpp (not sure about the origin of
this and the following three)
   - ./query_execution/ForemanDistributed.hpp
   - ./query_execution/PolicyEnforcerDistributed.cpp
   - ./query_execution/PolicyEnforcerDistributed.hpp
   - We checked the KEYS in the svn repo against the signed artifact and the
sig is fine, it was just my info which was old on the people.apache site ->
now updated.
   - Our website has been updated to include the logo and reword "apache
quickstep (incubating)".

In progress:
- We're reviewing what exactly goes in LICENSE/NOTICE files and will fix
them for the next release.


Feel free to ping if you'd like me to look over what you have put 
together before you spent time on the next RC. I can also provide some 
other examples of a LICENSE file which would look "similar".



Not Fixed:
   - Julian turned us on to a previous issue with pre-processed parser
files. It appears the content in /parser/preprocessed/ should be fine via
discussion on https://issues.apache.org/jira/browse/LEGAL-291


Thanks for this pointer! I thought something like this might have been 
the case (but was too lazy to parse it ;))




Thank you,
Marc


- Josh

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

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

2017-03-16 Thread Marc Spehlmann

Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating), everyone.
With this I will close the vote.

+1
Julian (binding)
Jignesh

-1
Josh (binding)

As we received one -1 binding vote, we will not release rc6.

___

The biggest issue seems to be our licensing checks.

Now Fixed:
  - third_party/src/cpplint/lint_everything.py
  - ./parser/preprocessed/genfiles.sh
  - ./query_execution/ForemanDistributed.cpp (not sure about the origin of
this and the following three)
  - ./query_execution/ForemanDistributed.hpp
  - ./query_execution/PolicyEnforcerDistributed.cpp
  - ./query_execution/PolicyEnforcerDistributed.hpp
  - We checked the KEYS in the svn repo against the signed artifact and the
sig is fine, it was just my info which was old on the people.apache site ->
now updated.
  - Our website has been updated to include the logo and reword "apache
quickstep (incubating)".

In progress:
- We're reviewing what exactly goes in LICENSE/NOTICE files and will fix
them for the next release.

Not Fixed:
  - Julian turned us on to a previous issue with pre-processed parser
files. It appears the content in /parser/preprocessed/ should be fine via
discussion on https://issues.apache.org/jira/browse/LEGAL-291

Thank you,
Marc


On Thu, Mar 16, 2017 at 3:08 PM, Josh Elser  wrote:

> -1 (binding)
>
> * xsums/sigs OK
>
> The key you provided isn't the one that was used to sign this release,
> FYI. You have D280F52E up on your people space, but used 5A29899A to sign
> this release.
>
> * Artifact starts with "apache-quickstep" and includes "incubating"
> * DISCLAIMER present
> * Missing LICENSE text for bundled software
> * Can build from source
>
> cpplint and glog are bundled and licensed under 3-clause BSD, but this
> text is not included in your LICENSE file. farmhash is MIT licensed and
> also not listed in your LICENSE file. When you create these entries in
> LICENSE, you can also move the copyright text from the NOTICE file and
> place it in the LICENSE file as a convenience.
>
> It appears that you bundle Google Protobuf and that is 3-clause BSD and
> also absent. Same for IWYU ("Include what you use").
>
> * `./parser/preprocessed/*` seems to be licensed as GPLv3 from the header
> which is a no-go.
>
> * Some missing/inaccurate license headers. Are these of Quickstep's
> creation? Bundled from somewhere else?
>   - third_party/src/cpplint/lint_everything.py (I'm guessing this is of
> your own creation, I don't see this in the cpplint github repo)
>   - ./parser/preprocessed/genfiles.sh
>   - ./query_execution/ForemanDistributed.cpp (not sure about the origin
> of this and the following three)
>   - ./query_execution/ForemanDistributed.hpp
>   - ./query_execution/PolicyEnforcerDistributed.cpp
>   - ./query_execution/PolicyEnforcerDistributed.hpp
>
> gflags is listed in NOTICE but not bundled (at least at the noted
> location). Strike this text or fix the location at which it is bundled.
>
> Aside: took a look at your website. A few comments:
>
> * ASF incubator text is there. Good work.
> * If you could include the incubator logo, that would also be good (per
> policy).
> * Typically podlings refer to themselves as "Apache Quickstep
> (incubating)" instead of "Apache (incubating) Quickstep" as in the header
> in the landing page :)
>
> Pretty close, but just a couple of bad licensing things to clean up here.
> Please feel free to ask if what I pointed out is unclear/wrong.
>
> - Josh
>
>
> Marc Spehlmann wrote:
>
>> The Apache Incubator Quickstep community has approved a vote to release
>> Quickstep-0.1.0 RC6. Quickstep is a high performance relational database
>> system built from the ground up for modern hardware.
>>
>> This vote will stay open until Wednesday 18:00 cst.
>>
>> -Marc
>> ___
>> The vote and results thread from dev:
>> https://lists.apache.org/thread.html/4da9e32fc24d7fc24b91795
>> 0760b726734c7023aa92da4e7fa16db85@%3Cdev.quickstep.apache.org%3E
>>
>> https://lists.apache.org/thread.html/6c8bbfd15504e4ff6d12404
>> 3a6c19c5463769cf495d69e0ef7825085@%3Cdev.quickstep.apache.org%3E
>>
>> The commit to be voted upon:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-quickste
>> p.git;a=commit;h=f8cf7fba51db3748c1c241c7e8880d499634213b
>>
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC6/
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/spehl
>>
>>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread siddharth anand

+1 (non-binding)

On Thu, Mar 16, 2017 at 12:46 PM, Jakob Homan  wrote:

> +1 binding.
>
> md5/asc/LICENSE/NOTICE/DISCLAIMER/headers all look good.
>
> NITs for next release:
> * setup.cfg still has Maxime listed as author and email.
> * usually the artifacts are named apache-whatever, rather than
> whatever-apache.
>
> Thanks,
> Jakob
>
>
> On 16 March 2017 at 10:46, Maxime Beauchemin 
> wrote:
> > +1 (non-binding)
> >
> > On Thu, Mar 16, 2017 at 9:59 AM, Jeremiah Lowin 
> wrote:
> >
> >> +1 (non-binding)
> >>
> >>
> >> On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer 
> wrote:
> >>
> >> > +1 (non-binding)
> >> >
> >> > Best,
> >> > Arthur
> >> >
> >> > On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini <
> criccom...@apache.org>
> >> > wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
> >> > wrote:
> >> > >
> >> > > > 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
> >> > > > 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> >> > > > 135caf930...@gmail.com%3e  >> > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> >> > > 3CB1833A3A-05FB-4112-B395-
> >> > > > 135caf930...@gmail.com%3E>
> >> > > >
> >> > > > *[RESULT][VOTE] Thread:*
> >> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> >> > > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> >> > > > b2273660a...@gmail.com%3e  >> > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> >> > > 3c59BC8C2B-12E2-4DE3-9555-
> >> > > > b2273660a...@gmail.com%3e>
> >> > > >
> >> > > > *The release candidate(s) to be voted on is available at:*
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz <
> https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > apache.incubating.tar.gz
> >> > > > >
> >> > > >
> >> > > > *Git branch*
> >> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> >> > > > 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 <
> >> > > > 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>
> >> > > >
> >> > > > *Git tag*
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> >> > > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> >> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> >> > > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76ef
> a42d0b6bb2>
> >> > > >
> >> > > > PGP signature
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
> >> > https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > > apache.incubating.tar.gz.asc>
> >> > > >
> >> > > > MD5/SHA Hashes:
> >> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> >> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
> >> > https://dist.apache.org/
> >> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> >> > > > apache.incubating.tar.gz.md5>
> >> > > >

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

-1 (binding)

* xsums/sigs OK

The key you provided isn't the one that was used to sign this release,
FYI. You have D280F52E up on your people space, but used 5A29899A to
sign this release.

* Artifact starts with "apache-quickstep" and includes "incubating"
* DISCLAIMER present
* Missing LICENSE text for bundled software
* Can build from source

cpplint and glog are bundled and licensed under 3-clause BSD, but this
text is not included in your LICENSE file. farmhash is MIT licensed and
also not listed in your LICENSE file. When you create these entries in
LICENSE, you can also move the copyright text from the NOTICE file and
place it in the LICENSE file as a convenience.

It appears that you bundle Google Protobuf and that is 3-clause BSD and
also absent. Same for IWYU ("Include what you use").

* `./parser/preprocessed/*` seems to be licensed as GPLv3 from the
header which is a no-go.

* Some missing/inaccurate license headers. Are these of Quickstep's
creation? Bundled from somewhere else?
- third_party/src/cpplint/lint_everything.py (I'm guessing this is of
your own creation, I don't see this in the cpplint github repo)

- ./parser/preprocessed/genfiles.sh
- ./query_execution/ForemanDistributed.cpp (not sure about the origin
of this and the following three)

- ./query_execution/ForemanDistributed.hpp
- ./query_execution/PolicyEnforcerDistributed.cpp
- ./query_execution/PolicyEnforcerDistributed.hpp

gflags is listed in NOTICE but not bundled (at least at the noted
location). Strike this text or fix the location at which it is bundled.

Aside: took a look at your website. A few comments:

* ASF incubator text is there. Good work.
* If you could include the incubator logo, that would also be good (per
policy).
* Typically podlings refer to themselves as "Apache Quickstep
(incubating)" instead of "Apache (incubating) Quickstep" as in the
header in the landing page :)

Pretty close, but just a couple of bad licensing things to clean up
here. Please feel free to ask if what I pointed out is unclear/wrong.

- Josh

Marc Spehlmann wrote:

The Apache Incubator Quickstep community has approved a vote to release
Quickstep-0.1.0 RC6. Quickstep is a high performance relational database
system built from the ground up for modern hardware.

This vote will stay open until Wednesday 18:00 cst.

-Marc
___
The vote and results thread from dev:
https://lists.apache.org/thread.html/4da9e32fc24d7fc24b917950760b726734c7023aa92da4e7fa16db85@%3Cdev.quickstep.apache.org%3E

https://lists.apache.org/thread.html/6c8bbfd15504e4ff6d124043a6c19c5463769cf495d69e0ef7825085@%3Cdev.quickstep.apache.org%3E

The commit to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=commit;h=f8cf7fba51db3748c1c241c7e8880d499634213b

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

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

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

Re: [VOTE] Apache Slider (incubating) release 0.92.0-incubating

2017-03-16 Thread Billie Rinaldi

Here is my +1 binding from the PPMC vote.

On Wed, 15 Mar 2017 23:15:40, Gour Saha wrote:

> Hello,
>
> This is a call for a vote on the Apache Slider (incubating) release
> 0.92.0-incubating.
>
> This release candidate, 0.92.0-incubating-RC0 has successfully passed a
> vote for a release on the slider developer mailing list.
>
> Vote thread:
>http://mail-archives.apache.org/mod_mbox/incubator-slider-d
> ev/201703.mbox/%3CD4E792AE.2693A%25gsaha%40hortonworks.com%3E
>
> Results:
>http://mail-archives.apache.org/mod_mbox/incubator-slider-d
> ev/201703.mbox/%3CD4EEB66E.26E31%25gsaha%40hortonworks.com%3E
>
> Source artifacts:
>https://dist.apache.org/repos/dist/dev/incubator/
> slider/0.92.0-incubating-RC0
>
> Staged artifacts:
>https://repository.apache.org/content/repositories/orgap
> acheslider-1017/
>
> Git source:
>https://git-wip-us.apache.org/repos/asf?p=incubator-
> slider.git;a=commit;h=c41b1c7051d02c02b0d78cab859c7e15d0af92c9
>
> Git commit SHA1: c41b1c7051d02c02b0d78cab859c7e15d0af92c9
>
> Issues fixed:
>https://issues.apache.org/jira/browse/SLIDER/fixforversion/12339846/
>
> Release Notes:
>https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
> ectId=12315422=12339846
>
> PGP key:
>http://pgp.mit.edu:11371/pks/lookup?op=vindex=gourks
> a...@apache.org
>
> Please vote on releasing this package as Apache Slider 0.92.0-incubating:
>
> This vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> gourksaha on behalf of the Apache Slider (incubating) team
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Jakob Homan

+1 binding.

md5/asc/LICENSE/NOTICE/DISCLAIMER/headers all look good.

NITs for next release:
* setup.cfg still has Maxime listed as author and email.
* usually the artifacts are named apache-whatever, rather than whatever-apache.

Thanks,
Jakob


On 16 March 2017 at 10:46, Maxime Beauchemin  wrote:
> +1 (non-binding)
>
> On Thu, Mar 16, 2017 at 9:59 AM, Jeremiah Lowin  wrote:
>
>> +1 (non-binding)
>>
>>
>> On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer  wrote:
>>
>> > +1 (non-binding)
>> >
>> > Best,
>> > Arthur
>> >
>> > On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini 
>> > wrote:
>> >
>> > > +1 (non-binding)
>> > >
>> > > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
>> > wrote:
>> > >
>> > > > 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
>> > > > 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
>> > > > 135caf930...@gmail.com%3e > > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
>> > > 3CB1833A3A-05FB-4112-B395-
>> > > > 135caf930...@gmail.com%3E>
>> > > >
>> > > > *[RESULT][VOTE] Thread:*
>> > > > http://mail-archives.apache.org/mod_mbox/incubator-
>> > > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
>> > > > b2273660a...@gmail.com%3e > > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
>> > > 3c59BC8C2B-12E2-4DE3-9555-
>> > > > b2273660a...@gmail.com%3e>
>> > > >
>> > > > *The release candidate(s) to be voted on is available at:*
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> > > > airflow-1.8.0rc5+apache.incubating.tar.gz > > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
>> > > apache.incubating.tar.gz
>> > > > >
>> > > >
>> > > > *Git branch*
>> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
>> > > > 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 <
>> > > > 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>
>> > > >
>> > > > *Git tag*
>> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
>> > > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
>> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
>> > > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
>> > > >
>> > > > PGP signature
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
>> > https://dist.apache.org/
>> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
>> > > > apache.incubating.tar.gz.asc>
>> > > >
>> > > > MD5/SHA Hashes:
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
>> > https://dist.apache.org/
>> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
>> > > > apache.incubating.tar.gz.md5>
>> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.sha <
>> > https://dist.apache.org/
>> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
>> > > > apache.incubating.tar.gz.sha>
>> > > >
>> > > > *Keys to verify the signature of the release artifacts are available
>> > at:*
>> > > >

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

2017-03-16 Thread Vinod Kumar Vavilapalli

Great work, Atlas community!

Looked at the release, albeit a little late, per my check-list. We can look at 
the Side notes lines for the next release.

 - Can compile from the release tag, skipping unit-tests: mvn clean install 
-DskipTests
   — Side notes: The compilation takes a long time, may be because I was 
starting off a relatively clean .m2
 - Creating the package: mvn clean package -DskipTests passes.
— The package name looks good: 
./distro/target/apache-atlas-0.8-incubating-sources.tar.gz / 
./distro/target/apache-atlas-0.8-incubating-bin.tar.gz
— Side notes: mvn package after mvn clean install fails.
 - Rat check is good
— mvn clean verify -DskipTests passes
— Side notes: Though I expected "mvn apache-rat:check” to work
 - Integrity
— KEYS present on 
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS
— Checksum checks out. In Hadoop, we generate other hashes too via a .mds 
file (gpg2 --print-mds). For future.
— Release signatures look okay
 - LICENSE, NOTICE, DISCLAIMER files are located right
 - Side note: Publish info about maven artifacts for downstream users?

+1 binding.

Thanks
+Vinod

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

Re: [VOTE] Apache Slider (incubating) release 0.92.0-incubating


+1 (binding)

* xsums/sigs OK -- might want to start including sha256
* Spot-checked L
* DISCLAIMER present
* Can build from source
* `mvn apache-rat:check -Prat` passes
* Spot-checked the list of included files

Sorry I missed this VOTE while on the podling list :). Thanks, Gour!

- Josh

Gour Saha wrote:

Hello,

This is a call for a vote on the Apache Slider (incubating) release 
0.92.0-incubating.

This release candidate, 0.92.0-incubating-RC0 has successfully passed a vote 
for a release on the slider developer mailing list.

Vote thread:
   
http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4E792AE.2693A%25gsaha%40hortonworks.com%3E

Results:
   
http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4EEB66E.26E31%25gsaha%40hortonworks.com%3E

Source artifacts:
   https://dist.apache.org/repos/dist/dev/incubator/slider/0.92.0-incubating-RC0

Staged artifacts:
   https://repository.apache.org/content/repositories/orgapacheslider-1017/

Git source:
   
https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=c41b1c7051d02c02b0d78cab859c7e15d0af92c9

Git commit SHA1: c41b1c7051d02c02b0d78cab859c7e15d0af92c9

Issues fixed:
   https://issues.apache.org/jira/browse/SLIDER/fixforversion/12339846/

Release Notes:
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315422=12339846

PGP key:
   http://pgp.mit.edu:11371/pks/lookup?op=vindex=gourks...@apache.org

Please vote on releasing this package as Apache Slider 0.92.0-incubating:

This vote will be open for 72 hours.

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

gourksaha on behalf of the Apache Slider (incubating) team




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

Re: [VOTE] Release Apache Mynewt 1.0.0-incubating-rc1

2017-03-16 Thread Sterling Hughes

Hi All - I know there is a lot going on, but I’m hoping for some help 
getting this release out!


Thanks,

Sterling

On 14 Mar 2017, at 14:17, Sterling Hughes wrote:


+1 binding

On 12 Mar 2017, at 21:09, marko kiiskila wrote:


The Apache Mynewt Incubator PPMC has approved a proposal to release
Apache Mynewt 1.0.0-incubating-rc1. We now kindly request that the
Incubator PMC members review and vote on this incubator release.

Apache Mynewt is a community-driven, permissively licensed open 
source

initiative for constrained, embedded applications.  Mynewt provides a
real-time operating system, flash file system, network stacks, and
support utilities for real-world embedded systems.

For full release notes, please visit the Apache Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes 



[VOTE] thread:
https://lists.apache.org/thread.html/030cd65553128847b6931b3e32e0536326036ce9f332feb988759f55@%3Cdev.mynewt.apache.org%3E 



[RESULT][VOTE] thread:
https://lists.apache.org/thread.html/e863e81c7b4af0981610775d541f2a51a6814e4523fd74e1a402341a@%3Cdev.mynewt.apache.org%3E 



[DISCUSS] thread:
https://lists.apache.org/thread.html/f2e3c8bc63a377dd628a2bdafb7b160868525a134f75d766d7244578@%3Cdev.mynewt.apache.org%3E 



This release candidate was tested as follows:
 1. Manual execution of the Mynewt test plan:
https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan 


The test results can be found at:
https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0+Test+Results 


 2. The full unit test suite for this release was executed via "newt
test all" with no failures.  This testing was performed on the
following platforms:
  * OS X 10.12.3
  * Linux Ubuntu 14.04.4

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/ 



The commits under consideration are as follows:
blinky:
 repos: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky 


 commit 15496854000a2b0cc9d19c05e069d18be313fa28
core:
 repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core 


 commit 0db6321a75deda126943aa187842da6b977cd1c1
newt:
 repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt 


 commit c42ebdce8c278a00fa8d68ed342c45cd22e44dfb

In addition, the following newt convenience binaries are available:
 linux: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-linux-1.0.0-incubating.tgz 

 osx: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-osx-1.0.0-incubating.tgz 



The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS 



The vote is open for at least 72 hours and passes if a majority of at
least three +1 PPMC votes are cast.
[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because…

—
M


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

Re: [VOTE] Apache Incubator Quickstep 0.1.0 RC6

2017-03-16 Thread Marc Spehlmann

Incubator PMC,

There is one +1 so far (thank you Julian). Can you please review Apache
Quickstepstep 0.1.0 (incubating) RC6 and vote?

Thank you,
Marc

On Wed, Mar 15, 2017 at 11:37 AM, Julian Hyde  wrote:

> IPMC members, this podling (like all podlings) deserves a timely vote
> on their efforts. But 2.5 days into the vote, we have only one binding
> vote. If you are an IPMC member and have not voted on a podling
> release recently, now is the time to step up. Let's not rely on the
> diligence of John and Justin yet again.
>
> Julian
>
>
> On Wed, Mar 15, 2017 at 8:38 AM, Jignesh Patel 
> wrote:
> > Will do. Thanks Julian for pointing this out, and an even bigger thank
> you for being an amazing mentor!
> >
> > Cheers,
> > Jignesh
> >
> > On 3/14/17, 4:30 PM, "Julian Hyde"  wrote:
> >
> > Jignesh,
> >
> > Your vote is binding on the dev list vote (because you are a member
> of Quickstep PPMC) but not binding on this incubator vote (because you are
> not a member of the Incubator PMC).
> >
> > Your vote is still welcome, but in future please mark it
> “(non-binding)”.
> >
> > Julian
> >
> > > On Mar 14, 2017, at 7:24 AM, Jignesh Patel <
> jmp.quicks...@gmail.com> wrote:
> > >
> > > Forwarding my +1 (binding) from the dev list.
> > >
> > >
> > >
> > > On 3/10/17, 1:25 PM, "Jignesh Patel" 
> wrote:
> > >
> > >
> > >
> > > +1 (binding).
> > >
> > >
> > >
> > > On 3/8/17, 4:16 PM, "Marc Spehlmann" 
> wrote:
> > >
> > >
> > >
> > > This vote is for approval of the Quickstep-0.1.0 RC6.
> > >
> > >
> > >
> > > Voters should download, unpack, build, and test the
> package before voting.
> > >
> > >
> > >
> > > +1 vote should be accompanied with what you did with the
> release.
> > >
> > > -1 vote should be accompanied with a short reason.
> > >
> > >
> > >
> > > Votes will remain open for 3 days.
> > >
> > >
> > >
> > > ___
> > >
> > >
> > >
> > > Changes since RC5:
> > >
> > > - Vote email has been refactored. Added a template on the
> confluence wiki.
> > >
> > > - Removed KEYS file from the main github repo. It now
> exists as a single
> > >
> > > source of truth in the SVN repo for release artifacts. I
> updated the KEYS
> > >
> > > file to conform to the apache standard.
> > >
> > > - We'll now use sha256, sha512, and md5 to hash the
> artifacts
> > >
> > > - Created History.md file
> > >
> > > - Added additional headers based on RAT's output
> > >
> > > - Removed references to Pivotal
> > >
> > >
> > >
> > > SHA512
> > >
> > > c0cfffb701680ab3a8277f9e1c64f0
> a91a53e6eb6c32321c67a10aaed65557651d2495ed9503b845d41ab02a1b
> fb8f4d1481c5bbe270240a4ca702687a87e860
> > >
> > >  apache-quickstep-incubating-0.1.0.tar.gz
> > >
> > >
> > >
> > > ___
> > >
> > >
> > >
> > > The commit to be voted upon:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> quickstep.git;a=commit;h=f8cf7fba51db3748c1c241c7e8880d499634213b
> > >
> > >
> > >
> > > The artifacts to be voted on are located here:
> > >
> > > https://dist.apache.org/repos/
> dist/dev/incubator/quickstep/0.1.0/RC6/
> > >
> > >
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/spehl
> > >
> > >
> > >
> > > Please vote on releasing this package as Apache Incubating
> Quickstep 0.1.0.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Marc Spehlmann 
> > >
> > > Date: Fri, Mar 10, 2017 at 6:36 PM
> > > Subject: [VOTE] Apache Incubator Quickstep 0.1.0 RC6
> > > To: general@incubator.apache.org
> > >
> > >
> > > The Apache Incubator Quickstep community has approved a vote to
> release Quickstep-0.1.0 RC6. Quickstep is a high performance relational
> database system built from the ground up for modern hardware.
> > >
> > >
> > >
> > > This vote will stay open until Wednesday 18:00 cst.
> > >
> > >
> > >
> > > -Marc
> > >
> > > ___
> > >
> > > The vote and results thread from dev:
> > >
> > > https://lists.apache.org/thread.html/
> 4da9e32fc24d7fc24b917950760b726734c7023aa92da4e7fa16db85@%
> 3Cdev.quickstep.apache.org%3E
> > >
> > >
> > >
> > > https://lists.apache.org/thread.html/
>

[RESULT][VOTE] Release of Apache Tephra-0.11.0-incubating [rc2]

2017-03-16 Thread Gokul Gunasekaran

Hi all,

After being open for over 72 hours, the vote for releasing Apache Tephra
0.11.0-incubating [rc2] passed with 3 binding +1s and no 0 or -1.

Binding +1s:
James Taylor
Alan Gates
Andrew Purtell

Thanks to everyone who voted!

Thanks,
Gokul

On Wed, Mar 15, 2017 at 6:14 PM, Andrew Purtell  wrote:

> +1
>
> Unpacked source tarball, layout looks ok.
> Checked sums and signature: ok
> LICENSE and NOTICE: ok
> DISCLAIMER: ok
> RAT check passes: ok
> Built from source: ok (7u80)
> Unit tests pass: ok (7u80)
>
>
> On Fri, 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/%3CCAFgkoWEhJrFB5WdUJBh3qe5v9Uq
> YxPHLRQRJQBKUr7gD%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
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Maxime Beauchemin

+1 (non-binding)

On Thu, Mar 16, 2017 at 9:59 AM, Jeremiah Lowin  wrote:

> +1 (non-binding)
>
>
> On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer  wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Arthur
> >
> > On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini 
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
> > wrote:
> > >
> > > > 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
> > > > 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> > > > 135caf930...@gmail.com%3e  > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > > 3CB1833A3A-05FB-4112-B395-
> > > > 135caf930...@gmail.com%3E>
> > > >
> > > > *[RESULT][VOTE] Thread:*
> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> > > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> > > > b2273660a...@gmail.com%3e  > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > > 3c59BC8C2B-12E2-4DE3-9555-
> > > > b2273660a...@gmail.com%3e>
> > > >
> > > > *The release candidate(s) to be voted on is available at:*
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz  > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > apache.incubating.tar.gz
> > > > >
> > > >
> > > > *Git branch*
> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> > > > 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 <
> > > > 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>
> > > >
> > > > *Git tag*
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> > > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
> > > >
> > > > PGP signature
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > apache.incubating.tar.gz.asc>
> > > >
> > > > MD5/SHA Hashes:
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > apache.incubating.tar.gz.md5>
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.sha <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > 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/ <
> > > > 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 <
> > > > https://travis-ci.org/apache/incubator-airflow/builds/203106493>)
> but
> > > can
> > > > also be run manually by issuing “sh scripts/ci/check-license.sh” from

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Jeremiah Lowin

+1 (non-binding)


On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer  wrote:

> +1 (non-binding)
>
> Best,
> Arthur
>
> On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini 
> wrote:
>
> > +1 (non-binding)
> >
> > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
> wrote:
> >
> > > 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
> > > 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> > > 135caf930...@gmail.com%3e  > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > 3CB1833A3A-05FB-4112-B395-
> > > 135caf930...@gmail.com%3E>
> > >
> > > *[RESULT][VOTE] Thread:*
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> > > b2273660a...@gmail.com%3e  > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > 3c59BC8C2B-12E2-4DE3-9555-
> > > b2273660a...@gmail.com%3e>
> > >
> > > *The release candidate(s) to be voted on is available at:*
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > airflow-1.8.0rc5+apache.incubating.tar.gz  > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > apache.incubating.tar.gz
> > > >
> > >
> > > *Git branch*
> > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> > > 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 <
> > > 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>
> > >
> > > *Git tag*
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
> > >
> > > PGP signature
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
> https://dist.apache.org/
> > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > apache.incubating.tar.gz.asc>
> > >
> > > MD5/SHA Hashes:
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
> https://dist.apache.org/
> > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > apache.incubating.tar.gz.md5>
> > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > airflow-1.8.0rc5+apache.incubating.tar.gz.sha <
> https://dist.apache.org/
> > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > 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/ <
> > > 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 <
> > > 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

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Arthur Wiedmer

+1 (non-binding)

Best,
Arthur

On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini 
wrote:

> +1 (non-binding)
>
> On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin  wrote:
>
> > 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
> > 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> > 135caf930...@gmail.com%3e  > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> 3CB1833A3A-05FB-4112-B395-
> > 135caf930...@gmail.com%3E>
> >
> > *[RESULT][VOTE] Thread:*
> > http://mail-archives.apache.org/mod_mbox/incubator-
> > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> > b2273660a...@gmail.com%3e  > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> 3c59BC8C2B-12E2-4DE3-9555-
> > b2273660a...@gmail.com%3e>
> >
> > *The release candidate(s) to be voted on is available at:*
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > airflow-1.8.0rc5+apache.incubating.tar.gz  > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> apache.incubating.tar.gz
> > >
> >
> > *Git branch*
> > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> > 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 <
> > 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>
> >
> > *Git tag*
> > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
> >
> > PGP signature
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > airflow-1.8.0rc5+apache.incubating.tar.gz.asc  > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > apache.incubating.tar.gz.asc>
> >
> > MD5/SHA Hashes:
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > airflow-1.8.0rc5+apache.incubating.tar.gz.md5  > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > apache.incubating.tar.gz.md5>
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > airflow-1.8.0rc5+apache.incubating.tar.gz.sha  > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > 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/ <
> > 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 <
> > 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
> >
>

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

2017-03-16 Thread Chris Riccomini

+1 (non-binding)

On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin  wrote:

> 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
> 5. 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/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> 135caf930...@gmail.com%3e  org/mod_mbox/incubator-airflow-dev/201703.mbox/%3CB1833A3A-05FB-4112-B395-
> 135caf930...@gmail.com%3E>
>
> *[RESULT][VOTE] Thread:*
> http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e  org/mod_mbox/incubator-airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> b2273660a...@gmail.com%3e>
>
> *The release candidate(s) to be voted on is available at:*
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> https://dist.apache.org/repos/dist/dev/incubator/airflow/
> airflow-1.8.0rc5+apache.incubating.tar.gz  repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+apache.incubating.tar.gz
> >
>
> *Git branch*
> https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> 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 <
> 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>
>
> *Git tag*
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
>
> PGP signature
> https://dist.apache.org/repos/dist/dev/incubator/airflow/
> airflow-1.8.0rc5+apache.incubating.tar.gz.asc  repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> apache.incubating.tar.gz.asc>
>
> MD5/SHA Hashes:
> https://dist.apache.org/repos/dist/dev/incubator/airflow/
> airflow-1.8.0rc5+apache.incubating.tar.gz.md5  repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> apache.incubating.tar.gz.md5>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/
> airflow-1.8.0rc5+apache.incubating.tar.gz.sha  repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> 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/ <
> 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 <
> 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
>

[VOTE] Release Apache Airflow 1.8.0 (incubating)