Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <1BA62FD0-851A-43BB-965E-87B680E247B6@gmail.com>
References: <1BA62FD0-851A-43BB-965E-87B680E247B6@gmail.com>
From: Boris Tyukin <boris@boristyukin.com>
Date: Thu, 2 Feb 2017 15:52:57 -0500
Message-ID: <CANRT7T1XVsB67=+dXN7qYAHSDPhxTbzz-K=w4_H5KHqFR3iCKA@mail.gmail.com>
Subject: Re: Airflow 1.8.0 Release Candidate 1
To: dev@airflow.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113f933869d69d0547925b0d
archived-at: Thu, 02 Feb 2017 20:54:28 -0000

--001a113f933869d69d0547925b0d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Bolke, you are our hero! I am sure you put a lot of your time to make it
happen

On Thu, Feb 2, 2017 at 2:50 PM, Bolke de Bruin <bdbruin@gmail.com> wrote:

> Hi All,
>
> I have made the (first) RELEASE CANDIDATE of Airflow 1.8.0 available at:
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ , public keys
> are available at https://dist.apache.org/repos/dist/release/incubator/
> airflow/ . It is tagged with a local version =E2=80=9Capache.incubating=
=E2=80=9D so it
> allows upgrading from earlier releases. This should be considered of
> release quality, but not yet officially vetted as a release yet.
>
> Issues fixed:
> * Use static nvd3 and d3
> * Python 3 incompatibilities
> * CLI API trigger dag issue
>
> As the difference between beta 5 and the release candidate is relatively
> small I hope to start the VOTE for releasing 1.8.0 quite soon (2 days?), =
if
> the vote passes also a vote needs to happen at the IPMC mailinglist. As
> this is our first Apache release I expect some comments and required
> changes and probably a RC 2.
>
> Furthermore, we now have a =E2=80=9Cv1-8-stable=E2=80=9D branch. This has=
 version
> =E2=80=9C1.8.0rc1=E2=80=9D and will graduate to =E2=80=9C1.8.0=E2=80=9D w=
hen we release. The =E2=80=9Cv1-8-test=E2=80=9D
> branch now has version =E2=80=9C1.8.1alpha0=E2=80=9D as version and =E2=
=80=9Cmaster=E2=80=9D has version
> =E2=80=9C1.9.0dev0=E2=80=9D. Note that =E2=80=9Cv1-8-stable=E2=80=9D is n=
ow closed. This means that, per
> release guidelines, patches accompanied with an ASSIGNED Jira and a
> sign-off from a committer. Only then the release manager applies the patc=
h
> to stable (In this case that would be me). The release manager then close=
s
> the bug when the patches have landed in the appropriate branches. For mor=
e
> information please see: https://cwiki.apache.org/
> confluence/display/AIRFLOW/Airflow+Release+Planning+and+
> Supported+Release+Lifetime <https://cwiki.apache.org/
> confluence/display/AIRFLOW/Airflow+Release+Planning+and+
> Supported+Release+Lifetime> .
>
> Any questions or suggestions don=E2=80=99t hesitate to ask!
>
> Cheers
> Bolke

--001a113f933869d69d0547925b0d--