+1 (binding) Ran through the basic checks.
Minor nit which can be fixed in the next release: there are a bunch of documentation files which could have a license header added (e.g. .md, .rst, ) thanks Hitesh On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin <bdbr...@gmail.com> wrote: > Sorry Willem that should be of course. Apologies. > > Sent from my iPhone > > > On 20 Aug 2018, at 13:07, Bolke de Bruin <bdbr...@gmail.com> wrote: > > > > Hi William > > > > You seem to be missing a "4" at the end of the URL? Ah it seems that my > original email had a quirk. Would you mind using the below? > > > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 > > > > Thanks! > > Bolke > > > > Sent from my iPhone > > > >> On 20 Aug 2018, at 13:03, Willem Jiang <willem.ji...@gmail.com> wrote: > >> > >> Hi, > >> > >> The Git tag cannot be accessed. I can only get the 404 error there. > >> > >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >>> On Sun, Aug 12, 2018 at 8:25 PM, 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.10.0 (incubating) based on 1.10.0 Release Candidate > 4. We > >>> now kindly request the Incubator PMC members to review and vote on this > >>> incubator release. > >>> > >>> 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. > >>> > >>> After a successful IPMC vote Artifacts will be available at: > >>> > >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow < > >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow> > >>> > >>> Public keys are available at: > >>> > >>> https://www.apache.org/dist/incubator/airflow/ < > >>> https://www.apache.org/dist/incubator/airflow/> > >>> > >>> apache-airflow-1.10.0rc4+incubating-source.tar.gz > >>> > >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > >>> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > >>> airflow-1.10.0rc4+incubating-source.tar.gz> > >>> > >>> is a source release that comes with INSTALL instructions. Along with > it, > >>> for > >>> convenience, find the binary Python "sdist" as > >>> apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > >>> > >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > >>> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > >>> airflow-1.10.0rc4+incubating-bin.tar.gz> > >>> > >>> Vote thread: > >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ > >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ > >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > >>> > >>> Git tag: > >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > >>> > >>> The vote will be open for at least 72 hours and until the necessary > number > >>> of > >>> votes are reached. > >>> > >>> Members please be sure to indicate "(Binding)" with your vote which > will > >>> help in tallying the vote(s). > >>> > >>> * Here is my +1 (non-binding) * > >>> > >>> Cheers, > >>> Bolke > >>> > >>> * WARNING: Due to licensing requirements you will need to set > >>> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when > >>> installing or upgrading. We will try to remove this requirement for the > >>> next release. > >>> >
