Thank You Bolke for all the efforts you are putting in !! I have deployed this RC now.
On Thu, Feb 2, 2017 at 3:02 PM, Jeremiah Lowin <jlo...@apache.org> wrote: > Fantastic work on this Bolke, thank you! > > We've deployed the RC and will report if there are any issues... > > On Thu, Feb 2, 2017 at 4:32 PM Bolke de Bruin <bdbr...@gmail.com> wrote: > > > Now I am blushing :-) > > > > Sent from my iPhone > > > > > On 2 Feb 2017, at 22:05, Boris Tyukin <bo...@boristyukin.com> wrote: > > > > > > LOL awesome! > > > > > > On Thu, Feb 2, 2017 at 4:00 PM, Maxime Beauchemin < > > > maximebeauche...@gmail.com> wrote: > > > > > >> The Apache mailing doesn't support images so here's a link: > > >> > > >> http://i.imgur.com/DUkpjZu.png > > >> > > >> > > >> On Thu, Feb 2, 2017 at 12:52 PM, Boris Tyukin <bo...@boristyukin.com> > > >> wrote: > > >> > > >>> 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 <bdbr...@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 “apache.incubating” 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 “v1-8-stable” branch. This has version > > >>>> “1.8.0rc1” and will graduate to “1.8.0” when we release. The > > >> “v1-8-test” > > >>>> branch now has version “1.8.1alpha0” as version and “master” has > > >> version > > >>>> “1.9.0dev0”. Note that “v1-8-stable” is now 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 > > >>> patch > > >>>> to stable (In this case that would be me). The release manager then > > >>> closes > > >>>> the bug when the patches have landed in the appropriate branches. > For > > >>> more > > >>>> 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’t hesitate to ask! > > >>>> > > >>>> Cheers > > >>>> Bolke > > >>> > > >> > > >
