+1 (non-binding)

On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin <bdbr...@gmail.com> 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
>

Reply via email to