You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Bolke de Bruin <bd...@gmail.com> on 2018/08/12 12:13:59 UTC
[RESULT][VOTE] Airflow 1.10.0rc4
Hello,
Apache Airflow (incubating) 1.10.0 (based on RC4) has been accepted.
4 “+1” binding votes received:
- Ash Berlin-Taylor (binding)
- Naik Kaxil (binding)
- Bolke de Bruin (binding)
- Fokko Driesprong (binding)
1 “-1” non-binding:
- Daniel Imberman (non-binding)
My next step is to open a thread with the IPMC.
Cheers,
Bolke
> Begin forwarded message:
>
> From: Bolke de Bruin <bd...@gmail.com>
> Subject: Re: [VOTE] Airflow 1.10.0rc4
> Date: 10 August 2018 at 21:34:40 CEST
> To: dev@airflow.incubator.apache.org
>
> Thanks @ash
>
> @daniel: I understand your concern but as k8s is pretty new the impact will be relatively low of having the bug. Let’s have a 1.10.1 quickly after this one (he Fokko ;-) ) and make sure the fixes are targeted for that one. Can you please create JIRA issues for the things you mentioned?
>
> B.
>
> Verstuurd vanaf mijn iPad
>
>> Op 10 aug. 2018 om 11:27 heeft Ash Berlin-Taylor <as...@apache.org> het volgende geschreven:
>>
>> If we can't score fractions then, yes +1 :)
>>
>> (And this time sent from the correct email address. I'm really bad at driving a Mail client it turns out.)
>>
>> -ash
>>
>>> On 9 Aug 2018, at 19:22, Bolke de Bruin <bd...@gmail.com> wrote:
>>>
>>> 0.5?? Can we score fractions :-) ? Sorry I missed this Ash. I think Fokko really wants a 1.10.1 quickly so better include it then? Can you make your vote +1?
>>>
>>> Thx
>>> Bolke
>>>
>>>> On 9 Aug 2018, at 14:06, Ash Berlin-Taylor <as...@firemirror.com> wrote:
>>>>
>>>> +0.5 (binding) from me.
>>>>
>>>> Tested upgrading form 1.9.0 metadb on Py3.5. Timezones behaving themselves on Postgres. Have not tested the Rbac-based UI.
>>>>
>>>> https://github.com/apache/incubator-airflow/commit/d9fecba14c5eb56990508573a91b13ab27ca5153 <https://github.com/apache/incubator-airflow/commit/d9fecba14c5eb56990508573a91b13ab27ca5153> (expanding on UPDATING.md for Logging changes) isn't in the release, but would only affect people who look at the UPDATING.md in the source tarball, which isn't going to be very many - most people will check in the repo and just install via PyPi I'd guess?
>>>>
>>>> -ash
>>>>
>>>>> On 8 Aug 2018, at 19:21, Bolke de Bruin <bd...@gmail.com> wrote:
>>>>>
>>>>> Hey all,
>>>>>
>>>>> I have cut Airflow 1.10.0 RC4. This email is calling a vote on the release,
>>>>> which will last for 72 hours. Consider this my (binding) +1.
>>>>>
>>>>> Airflow 1.10.0 RC 4 is available at:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/ <https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/>
>>>>>
>>>>> apache-airflow-1.10.0rc4+incubating-source.tar.gz is a source release that
>>>>> comes with INSTALL instructions.
>>>>> apache-airflow-1.10.0rc4+incubating-bin.tar.gz is the binary Python "sdist"
>>>>> release.
>>>>>
>>>>> Public keys are available at:
>>>>>
>>>>> https://dist.apache.org/repos/dist/release/incubator/airflow/ <https://dist.apache.org/repos/dist/release/incubator/airflow/>
>>>>>
>>>>> The amount of JIRAs fixed is over 700. Please have a look at the changelog.
>>>>> Since RC3 the following has been fixed:
>>>>>
>>>>> [AIRFLOW-2870] Use abstract TaskInstance for migration
>>>>> [AIRFLOW-2859] Implement own UtcDateTime
>>>>> [AIRFLOW-2140] Don't require kubernetes for the SparkSubmit hook
>>>>> [AIRFLOW-2869] Remove smart quote from default config
>>>>> [AIRFLOW-2857] Fix Read the Docs env
>>>>>
>>>>> Please note that the version number excludes the `rcX` string as well
>>>>> as the "+incubating" string, so it's now simply 1.10.0. This will allow us
>>>>> to rename the artifact without modifying the artifact checksums when we
>>>>> actually release.
>>>>>
>>>>> WARNING: Due to licensing requirements you will need to set
>>>>> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when
>>>>> installing or upgrading. We will try to remove this requirement for the
>>>>> next release.
>>>>>
>>>>> Cheers,
>>>>> Bolke
>>>>
>>>
>>
Re: [RESULT][VOTE] Airflow 1.10.0rc4
Posted by Daniel Imberman <da...@gmail.com>.
@bolke ok sounds good. I'll get more info from the users to solidify the
ticket. Benefit of releasing as experimental :) (also luckily not causing
failed DAGs or lost data)
On Sun, Aug 12, 2018, 5:14 AM Bolke de Bruin <bd...@gmail.com> wrote:
> Hello,
>
> Apache Airflow (incubating) 1.10.0 (based on RC4) has been accepted.
>
> 4 “+1” binding votes received:
>
> - Ash Berlin-Taylor (binding)
> - Naik Kaxil (binding)
> - Bolke de Bruin (binding)
> - Fokko Driesprong (binding)
>
> 1 “-1” non-binding:
>
> - Daniel Imberman (non-binding)
>
> My next step is to open a thread with the IPMC.
>
> Cheers,
> Bolke
>
> > Begin forwarded message:
> >
> > From: Bolke de Bruin <bd...@gmail.com>
> > Subject: Re: [VOTE] Airflow 1.10.0rc4
> > Date: 10 August 2018 at 21:34:40 CEST
> > To: dev@airflow.incubator.apache.org
> >
> > Thanks @ash
> >
> > @daniel: I understand your concern but as k8s is pretty new the impact
> will be relatively low of having the bug. Let’s have a 1.10.1 quickly after
> this one (he Fokko ;-) ) and make sure the fixes are targeted for that one.
> Can you please create JIRA issues for the things you mentioned?
> >
> > B.
> >
> > Verstuurd vanaf mijn iPad
> >
> >> Op 10 aug. 2018 om 11:27 heeft Ash Berlin-Taylor <as...@apache.org> het
> volgende geschreven:
> >>
> >> If we can't score fractions then, yes +1 :)
> >>
> >> (And this time sent from the correct email address. I'm really bad at
> driving a Mail client it turns out.)
> >>
> >> -ash
> >>
> >>> On 9 Aug 2018, at 19:22, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>
> >>> 0.5?? Can we score fractions :-) ? Sorry I missed this Ash. I think
> Fokko really wants a 1.10.1 quickly so better include it then? Can you make
> your vote +1?
> >>>
> >>> Thx
> >>> Bolke
> >>>
> >>>> On 9 Aug 2018, at 14:06, Ash Berlin-Taylor <as...@firemirror.com>
> wrote:
> >>>>
> >>>> +0.5 (binding) from me.
> >>>>
> >>>> Tested upgrading form 1.9.0 metadb on Py3.5. Timezones behaving
> themselves on Postgres. Have not tested the Rbac-based UI.
> >>>>
> >>>>
> https://github.com/apache/incubator-airflow/commit/d9fecba14c5eb56990508573a91b13ab27ca5153
> <
> https://github.com/apache/incubator-airflow/commit/d9fecba14c5eb56990508573a91b13ab27ca5153>
> (expanding on UPDATING.md for Logging changes) isn't in the release, but
> would only affect people who look at the UPDATING.md in the source tarball,
> which isn't going to be very many - most people will check in the repo and
> just install via PyPi I'd guess?
> >>>>
> >>>> -ash
> >>>>
> >>>>> On 8 Aug 2018, at 19:21, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>>>
> >>>>> Hey all,
> >>>>>
> >>>>> I have cut Airflow 1.10.0 RC4. This email is calling a vote on the
> release,
> >>>>> which will last for 72 hours. Consider this my (binding) +1.
> >>>>>
> >>>>> Airflow 1.10.0 RC 4 is available at:
> >>>>>
> >>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/
> <https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/>
> >>>>>
> >>>>> apache-airflow-1.10.0rc4+incubating-source.tar.gz is a source
> release that
> >>>>> comes with INSTALL instructions.
> >>>>> apache-airflow-1.10.0rc4+incubating-bin.tar.gz is the binary Python
> "sdist"
> >>>>> release.
> >>>>>
> >>>>> Public keys are available at:
> >>>>>
> >>>>> https://dist.apache.org/repos/dist/release/incubator/airflow/ <
> https://dist.apache.org/repos/dist/release/incubator/airflow/>
> >>>>>
> >>>>> The amount of JIRAs fixed is over 700. Please have a look at the
> changelog.
> >>>>> Since RC3 the following has been fixed:
> >>>>>
> >>>>> [AIRFLOW-2870] Use abstract TaskInstance for migration
> >>>>> [AIRFLOW-2859] Implement own UtcDateTime
> >>>>> [AIRFLOW-2140] Don't require kubernetes for the SparkSubmit hook
> >>>>> [AIRFLOW-2869] Remove smart quote from default config
> >>>>> [AIRFLOW-2857] Fix Read the Docs env
> >>>>>
> >>>>> Please note that the version number excludes the `rcX` string as well
> >>>>> as the "+incubating" string, so it's now simply 1.10.0. This will
> allow us
> >>>>> to rename the artifact without modifying the artifact checksums when
> we
> >>>>> actually release.
> >>>>>
> >>>>> WARNING: Due to licensing requirements you will need to set
> >>>>> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when
> >>>>> installing or upgrading. We will try to remove this requirement for
> the
> >>>>> next release.
> >>>>>
> >>>>> Cheers,
> >>>>> Bolke
> >>>>
> >>>
> >>
>
>