Hey all,

I'm going to let this vote go bit longer.

Dan, Arthur, anyone else? Given the number of committers that we have, I
expect more votes.

Cheers,
Chris

On Wed, Nov 15, 2017 at 6:41 AM, Ash Berlin-Taylor <
[email protected]> wrote:

> https://issues.apache.org/jira/browse/AIRFLOW-1795 <
> https://issues.apache.org/jira/browse/AIRFLOW-1795> is still open which
> breaks a number of operators from Airflow 1.8.2 to 1.9.0:
>
> RedshiftToS3
> S3FileTransformOperator
> S3KeySensor
> S3PrefixSensor
> S3ToHive
>
> I present a couple of ways of solving that in the ticket, I'd like some
> feedback on which one people think is the best then I'll make the change.
>
> -ash
>
> > On 15 Nov 2017, at 13:48, Bolke de Bruin <[email protected]> wrote:
> >
> > Hi Chris,
> >
> > Your changelog seems incomplete (some more fixes were included in RC2).
> >
> > But apart from that
> >
> > +1, binding
> >
> > Bolke
> >
> >
> >> On 13 Nov 2017, at 19:03, Chris Riccomini <[email protected]>
> wrote:
> >>
> >> Hey all,
> >>
> >> I have cut Airflow 1.9.0 RC2. This email is calling a vote on the
> release,
> >> which will last for 72 hours. Consider this my (binding) +1.
> >>
> >> Airflow 1.9.0 RC2 is available at:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.9.0rc2/
> >>
> >> apache-airflow-1.9.0rc2+incubating-source.tar.gz is a source release
> that
> >> comes with INSTALL instructions.
> >> apache-airflow-1.9.0rc2+incubating-bin.tar.gz is the binary Python
> "sdist"
> >> release.
> >>
> >> Public keys are available at:
> >>
> >> https://dist.apache.org/repos/dist/release/incubator/airflow/
> >>
> >> The release contains the following JIRAs:
> >>
> >> https://issues.apache.org/jira/browse/AIRFLOW-1776
> >> https://issues.apache.org/jira/browse/AIRFLOW-1794
> >> https://issues.apache.org/jira/browse/AIRFLOW-1789
> >> https://issues.apache.org/jira/browse/AIRFLOW-1792
> >> https://issues.apache.org/jira/browse/AIRFLOW-1102
> >>
> >> Along with all JIRAs that were in 1.9.0RC1 (see previous VOTE email for
> >> full list).
> >>
> >> Cheers,
> >> Chris
> >
>
>

Reply via email to