@sebb, @henk are you now able to vote +1 or is there anything else we need to pickup before?
Cheers Bolke > On 20 Dec 2017, at 15:29, sebb <seb...@gmail.com> wrote: > > On 19 December 2017 at 18:42, Chris Riccomini <criccom...@apache.org > <mailto:criccom...@apache.org>> wrote: >>> Please don't use the ".sha" extension ; use ".sha1", ".sha256", or >> ".sha512" instead for : >> >> Done. >> >>> If development of 1.8.0-incubating (and/or 1.8.1-incubating) has stopped >> (because superseded by 1.8.2-incubating), please remove it from >> /dist/release/incubator/airflow/. >> >> Done. >> >>> The dist.apache.org URL is not for use by the general public; it is only >> intended as the staging area for Airflow developers during a release. >> >> @sebb, this is where I'm confused. Since you guys haven't approved the >> release yet, I was under the impression that we were still staging the >> release. Are you saying I should move the rc8 artifacts over to >> https://dist.apache.org/repos/dist/release/incubator/airflow/ now, before >> the IPMC has +1'd the release? > > Sorry, my bad. I misread the email. > > dist.a.o is the correct host to use for artifacts, sigs, hashes in a VOTE. > > Ideally the KEYS link should use www.a.o/dist <http://www.a.o/dist>, as the > keys are best > maintained in dist/release rather than dist/dev (the file only needs > to be updated to add new RM keys). > >> On Tue, Dec 19, 2017 at 8:35 AM, sebb <seb...@gmail.com> wrote: >> >>> On 18 December 2017 at 20:32, Chris Riccomini <criccom...@apache.org> >>> wrote: >>>> Hello Incubator PMC’ers, >>>> >>>> The Apache Airflow community has voted and approved the proposal to >>> release >>>> Apache Airflow 1.9.0 (incubating) based on 1.9.0 Release Candidate 8. 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. >>>> >>>> Artifacts are available at: >>>> >>>> https://dist.apache.org/repos/dist/dev/incubator/airflow >>> >>> The dist.apache.org URL is not for use by the general public; it is >>> only intended as the staging area for Airflow developers during a >>> release. >>> >>> Releases MUST use the ASF 3rd party mirror system: >>> >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow >>> See also: >>> http://www.apache.org/dev/release-download-pages.html#links >>> >>>> Public keys are available at: >>>> >>>> https://dist.apache.org/repos/dist/release/incubator/airflow >>> >>> Again, that is not allowed; only reference KEYS, sigs and hashes from >>> >>> https://www.apache.org/dist/incubator/airflow >>> >>>> apache-airflow-1.9.0rc8+incubating-source.tar.gz >>>> < >>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >>> 9.0rc8/apache-airflow-1.9.0rc8+incubating-source.tar.gz >>> >>> This must use closer.cgi as above >>> >>>>> >>>> is a source release that comes with INSTALL instructions. Along with it, >>> for >>>> convenience, find the binary Python "sdist" as >>>> apache-airflow-1.9.0rc8+incubating-bin.tar.gz >>>> < >>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >>> 9.0rc8/apache-airflow-1.9.0rc8+incubating-bin.tar.gz >>>>> >>>> >>>> Vote thread: >>>> https://mail-archives.apache.org/mod_mbox/incubator- >>> airflow-dev/201712.mbox/%3CCABYbY7ecu8F8sp%3DgvZrvW3knj%3DQpdCUZu- >>> Jh02KngjGOezhBKA%40mail.gmail.com%3E >>>> >>>> Git tag: >>>> https://github.com/apache/incubator-airflow/releases/tag/1.9.0rc8 >>>> >>>> The vote will be open for at least 72 hours or until necessary number of >>>> votes are reached. >>> >>> Nitpick: you cannot close the vote until 72 hours have elapsed even if >>> the required number of votes have already been cast. >>> >>>> 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, >>>> Chris >>> >>> --------------------------------------------------------------------- >>> 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 > <mailto:general-unsubscr...@incubator.apache.org> > For additional commands, e-mail: general-h...@incubator.apache.org > <mailto:general-h...@incubator.apache.org>
