FYI!
We had an issue with the 1.7.1 Pypi release on Friday and had to bump the
version on Pypi to *1.7.1.2*.

*1.7.1.2* is what you should install : Announcement
<https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements> updated
as well.
-s

On Fri, May 20, 2016 at 4:22 PM, Hitesh Shah <[email protected]> wrote:

> Given that this release is not an ASF voted release, can we please make
> sure that there is no confusion regarding that i.e. there are very clear
> docs/announcements that 1.7.1 is *not* a release from ASF incubation.
>
> For example, "
> https://github.com/apache/incubator-airflow/releases/tag/1.7.1” should
> not exist. Additionally, I had assumed that 1.7.1 would be tagged with
> 1.7.1-airbnb or something similar to reduce the confusion.
>
> thanks
> — Hitesh
>
> > On May 20, 2016, at 1:51 PM, Chris Riccomini <[email protected]>
> wrote:
> >
> > Special thanks to Dan, Arthur, and Maxime for doing a lot of the burn-in
> > work and validation on their clusters! Very excited to try this out.
> >
> > Also, when should we start on the next release? This one took so long
> that
> > there's actually a fair amount of stuff already on master that's not in
> > 1.7.1. Plus, if we expect 3-5 RCs, it might be better to start earlier
> > rather than later.
> >
> > On Fri, May 20, 2016 at 11:23 AM, siddharth anand <[email protected]>
> wrote:
> >
> >> Hi Folks!
> >> Release 1.7.1 is out with large bunch of stability fixes & new features
> -
> >> 214 commits to be precise as per CHANGELOG.txt
> >> <https://github.com/apache/incubator-airflow/blob/master/CHANGELOG.txt>
> >>
> >> You can install via Pypi <https://pypi.python.org/pypi/airflow/1.7.1>
> or
> >> via Git tag <
> >> https://github.com/apache/incubator-airflow/releases/tag/1.7.1>
> >>
> >> Special thanks goes to Dan Davydov @aoen <https://github.com/aoen> for
> >> shepherding this release, which has been a beast!
> >>
> >> -s (Sid) on behalf of your Apache Airflow Maintainers
> >> <https://cwiki.apache.org/confluence/display/AIRFLOW/Committers>
> >>
>
>

Reply via email to