Our staging looks good, all the DAGs there pass. +1 (binding) On Fri, Feb 10, 2017 at 10:21 AM, Chris Riccomini <[email protected]> wrote:
> Running in all environments. Will vote after the weekend to make sure > things are working properly, but so far so good. > > On Fri, Feb 10, 2017 at 6:05 AM, Bolke de Bruin <[email protected]> wrote: > > > Dear All, > > > > Let’s try again! > > > > I have made the THIRD RELEASE CANDIDATE of Airflow 1.8.0 available at: > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ < > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> , public keys > > are available at https://dist.apache.org/repos/dist/release/incubator/ > > airflow/ <https://dist.apache.org/repos/dist/release/incubator/airflow/> > > . It is tagged with a local version “apache.incubating” so it allows > > upgrading from earlier releases. > > > > Two issues have been fixed since release candidate 2: > > > > * trigger_dag could create dags with fractional seconds, not supported by > > logging and UI at the moment > > * local api client trigger_dag had hardcoded execution of None > > > > Known issue: > > * Airflow on kubernetes and num_runs -1 (default) can expose import > issues. > > > > I have extensively discussed this with Alex (reporter) and we consider > > this a known issue with a workaround available as we are unable to > > replicate this in a different environment. UPDATING.md has been updated > > with the work around. > > > > As these issues are confined to a very specific area and full unit tests > > were added I would also like to raise a VOTE for releasing 1.8.0 based on > > release candidate 3, i.e. just renaming release candidate 3 to 1.8.0 > > release. > > > > Please respond to this email by: > > > > +1,0,-1 with *binding* if you are a PMC member or *non-binding* if you > are > > not. > > > > Thanks! > > Bolke > > > > My VOTE: +1 (binding) >
