You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Chris Riccomini <cr...@apache.org> on 2017/11/10 16:27:02 UTC
[CANCEL][VOTE] Airflow 1.9.0rc1
Hey all,
I'm going to cancel the RC1 vote due to the -1's. I'm tracking the
following issues for RC2:
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-1787
https://issues.apache.org/jira/browse/AIRFLOW-1102
Cheers,
Chris
On Fri, Nov 10, 2017 at 1:25 AM, Ash Berlin-Taylor <
ash_airflowlist@firemirror.com> wrote:
> The other difference is that if you depend upon airflow in a module where
> you want to put it in the install_requires section of a setup.py (not an
> application which has a requirements.txt, say) you can't use a git tag. Or
> at least I couldn't get it working.
>
> It doesn't make a difference a lot of time, but it is occasionally useful.
>
> -ash
>
> > On 9 Nov 2017, at 23:08, Alek Storm <al...@gmail.com> wrote:
> >
> > It’s not a major difference, but installing from a git repo via pip
> > requires a completely different syntax, which complicates our tooling,
> e.g.:
> >
> > $ pip install 'apache-airflow[postgres,celery,rabbitmq]=={{version}}'
> >
> > $ pip install 'git+git://github.com/apache/
> incubator-airflow@{{version}}#egg=apache-airflow[postgres,celery,rabbitmq]
> '
> >
> > Alek
> >
> >
> > On Thu, Nov 9, 2017 at 3:53 PM, Arthur Wiedmer <arthur.wiedmer@gmail.com
> >
> > wrote:
> >
> >> I agree with Bolke that it would be better to provide dev releases in
> PyPI,
> >> but my understanding was that, while not an official release channel, it
> >> still has the apache branding and we should be careful nonetheless.
> >>
> >> I am still confused as to why installing from a git tag or the like is
> not
> >> OK for testing, provided our release artifact creation process is
> >> consistent.
> >>
> >> Best,
> >> Arthur
> >>
> >> On Thu, Nov 9, 2017 at 12:09 PM, Daniel Huang <dx...@gmail.com>
> wrote:
> >>
> >>> This is how pip handles RC/beta versions:
> >>>
> >>>
> >>>> Pre-release Versions
> >>>> Starting with v1.4, pip will only install stable versions as specified
> >> by
> >>>> PEP426 by default. If a version cannot be parsed as a compliant PEP426
> >>>> version then it is assumed to be a pre-release.
> >>>> If a Requirement specifier includes a pre-release or development
> >> version
> >>>> (e.g. >=0.0.dev0) then pip will allow pre-release and development
> >>> versions
> >>>> for that requirement. This does not include the != flag.
> >>>> The pip install command also supports a --pre flag that will enable
> >>>> installing pre-releases and development releases.
> >>>
> >>>
> >>> Source:
> >>> https://pip.pypa.io/en/stable/reference/pip_install/#pre-
> >> release-versions
> >>> <https://pip.pypa.io/en/stable/reference/pip_install/#
> >> pre-release-versions
> >>>>
> >>>
> >>> On Thu, Nov 9, 2017 at 11:54 AM, Bolke de Bruin <bd...@gmail.com>
> >> wrote:
> >>>
> >>>> I think we should put this up for discussion. PyPi is not an official
> >>>> apache channel, so in theory we could put anything on PyPI. I also
> >> think
> >>>> (didn’t confirm) pip doesn’t upgrade to RC/beta etc.
> >>>>
> >>>> Any thoughts?
> >>>>
> >>>> Bolke.
> >>>>
> >>>>> On 9 Nov 2017, at 15:53, Arthur Wiedmer <ar...@apache.org> wrote:
> >>>>>
> >>>>> Hi Alek,
> >>>>>
> >>>>> Technically, we cannot release a distribution on PyPI until we have
> >>> voted
> >>>>> on a release. And here usually a release artifact. It is a little
> >>>>> convoluted in the case of Python, but we are getting the hang of it.
> >>>>>
> >>>>> That said, installing from a git reference is a possibility too if
> >> you
> >>>> want
> >>>>> the fastest path to install.
> >>>>>
> >>>>> Best,
> >>>>> Arthur
> >>>>>
> >>>>> On Nov 9, 2017 06:34, "Alek Storm" <al...@gmail.com> wrote:
> >>>>>
> >>>>> I think this has been mentioned before, but it would be much easier
> >> for
> >>>> us
> >>>>> (my team) to test RCs if they were published to PyPI. Or is that
> >>> against
> >>>>> Apache guidelines?
> >>>>>
> >>>>> Alek
> >>>>>
> >>>>> On Thu, Nov 9, 2017 at 8:29 AM, Michael Crawford <
> >>>>> michael.crawford@modernizingmedicine.com> wrote:
> >>>>>
> >>>>>> Thanks. Yes I understand it isn’t released yet.
> >>>>>>
> >>>>>>
> >>>>>>> On Nov 9, 2017, at 9:09 AM, Driesprong, Fokko <fokko@driesprong.frl
> >>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi Michael,
> >>>>>>>
> >>>>>>> You have to install it from the tar.gz:
> >>>>>>>
> >>>>>>> wget
> >>>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.
> >>>>>> 9.0rc1/apache-airflow-1.9.0rc1+incubating-bin.tar.gz
> >>>>>>> pip install /tmp/apache-airflow.tar.gz
> >>>>>>>
> >>>>>>> The steps of updating, are in the UPDATING.md:
> >>>>>>> https://github.com/apache/incubator-airflow/blob/master/
> >> UPDATING.md
> >>>>>>>
> >>>>>>> Please note that 1.9 is not released yet, but you are welcome to
> >> try
> >>>> out
> >>>>>>> RC1.
> >>>>>>>
> >>>>>>> Cheers, Fokko
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: [CANCEL][VOTE] Airflow 1.9.0rc1
Posted by Chris Riccomini <cr...@apache.org>.
I will cut a release on Monday. :)
On Fri, Nov 10, 2017 at 11:35 AM, Bolke de Bruin <bd...@gmail.com> wrote:
> Hi Chris,
>
> It seems that all of them are merged into the 1.9.0-stable branch, except
> for one that is only committed to master.
>
> Can we get RC2 out?
>
> Bolke
>
> Sent from my iPhone
>
> > On 10 Nov 2017, at 17:27, Chris Riccomini <cr...@apache.org> wrote:
> >
> > Hey all,
> >
> > I'm going to cancel the RC1 vote due to the -1's. I'm tracking the
> > following issues for RC2:
> >
> > 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-1787
> > https://issues.apache.org/jira/browse/AIRFLOW-1102
> >
> > Cheers,
> > Chris
> >
> > On Fri, Nov 10, 2017 at 1:25 AM, Ash Berlin-Taylor <
> > ash_airflowlist@firemirror.com> wrote:
> >
> >> The other difference is that if you depend upon airflow in a module
> where
> >> you want to put it in the install_requires section of a setup.py (not an
> >> application which has a requirements.txt, say) you can't use a git tag.
> Or
> >> at least I couldn't get it working.
> >>
> >> It doesn't make a difference a lot of time, but it is occasionally
> useful.
> >>
> >> -ash
> >>
> >>> On 9 Nov 2017, at 23:08, Alek Storm <al...@gmail.com> wrote:
> >>>
> >>> It’s not a major difference, but installing from a git repo via pip
> >>> requires a completely different syntax, which complicates our tooling,
> >> e.g.:
> >>>
> >>> $ pip install 'apache-airflow[postgres,celery,rabbitmq]=={{version}}'
> >>>
> >>> $ pip install 'git+git://github.com/apache/
> >> incubator-airflow@{{version}}#egg=apache-airflow[postgres,
> celery,rabbitmq]
> >> '
> >>>
> >>> Alek
> >>>
> >>>
> >>> On Thu, Nov 9, 2017 at 3:53 PM, Arthur Wiedmer <
> arthur.wiedmer@gmail.com
> >>>
> >>> wrote:
> >>>
> >>>> I agree with Bolke that it would be better to provide dev releases in
> >> PyPI,
> >>>> but my understanding was that, while not an official release channel,
> it
> >>>> still has the apache branding and we should be careful nonetheless.
> >>>>
> >>>> I am still confused as to why installing from a git tag or the like is
> >> not
> >>>> OK for testing, provided our release artifact creation process is
> >>>> consistent.
> >>>>
> >>>> Best,
> >>>> Arthur
> >>>>
> >>>> On Thu, Nov 9, 2017 at 12:09 PM, Daniel Huang <dx...@gmail.com>
> >> wrote:
> >>>>
> >>>>> This is how pip handles RC/beta versions:
> >>>>>
> >>>>>
> >>>>>> Pre-release Versions
> >>>>>> Starting with v1.4, pip will only install stable versions as
> specified
> >>>> by
> >>>>>> PEP426 by default. If a version cannot be parsed as a compliant
> PEP426
> >>>>>> version then it is assumed to be a pre-release.
> >>>>>> If a Requirement specifier includes a pre-release or development
> >>>> version
> >>>>>> (e.g. >=0.0.dev0) then pip will allow pre-release and development
> >>>>> versions
> >>>>>> for that requirement. This does not include the != flag.
> >>>>>> The pip install command also supports a --pre flag that will enable
> >>>>>> installing pre-releases and development releases.
> >>>>>
> >>>>>
> >>>>> Source:
> >>>>> https://pip.pypa.io/en/stable/reference/pip_install/#pre-
> >>>> release-versions
> >>>>> <https://pip.pypa.io/en/stable/reference/pip_install/#
> >>>> pre-release-versions
> >>>>>>
> >>>>>
> >>>>> On Thu, Nov 9, 2017 at 11:54 AM, Bolke de Bruin <bd...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>>> I think we should put this up for discussion. PyPi is not an
> official
> >>>>>> apache channel, so in theory we could put anything on PyPI. I also
> >>>> think
> >>>>>> (didn’t confirm) pip doesn’t upgrade to RC/beta etc.
> >>>>>>
> >>>>>> Any thoughts?
> >>>>>>
> >>>>>> Bolke.
> >>>>>>
> >>>>>>> On 9 Nov 2017, at 15:53, Arthur Wiedmer <ar...@apache.org> wrote:
> >>>>>>>
> >>>>>>> Hi Alek,
> >>>>>>>
> >>>>>>> Technically, we cannot release a distribution on PyPI until we have
> >>>>> voted
> >>>>>>> on a release. And here usually a release artifact. It is a little
> >>>>>>> convoluted in the case of Python, but we are getting the hang of
> it.
> >>>>>>>
> >>>>>>> That said, installing from a git reference is a possibility too if
> >>>> you
> >>>>>> want
> >>>>>>> the fastest path to install.
> >>>>>>>
> >>>>>>> Best,
> >>>>>>> Arthur
> >>>>>>>
> >>>>>>> On Nov 9, 2017 06:34, "Alek Storm" <al...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> I think this has been mentioned before, but it would be much easier
> >>>> for
> >>>>>> us
> >>>>>>> (my team) to test RCs if they were published to PyPI. Or is that
> >>>>> against
> >>>>>>> Apache guidelines?
> >>>>>>>
> >>>>>>> Alek
> >>>>>>>
> >>>>>>> On Thu, Nov 9, 2017 at 8:29 AM, Michael Crawford <
> >>>>>>> michael.crawford@modernizingmedicine.com> wrote:
> >>>>>>>
> >>>>>>>> Thanks. Yes I understand it isn’t released yet.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Nov 9, 2017, at 9:09 AM, Driesprong, Fokko
> <fokko@driesprong.frl
> >>>>>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi Michael,
> >>>>>>>>>
> >>>>>>>>> You have to install it from the tar.gz:
> >>>>>>>>>
> >>>>>>>>> wget
> >>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.
> >>>>>>>> 9.0rc1/apache-airflow-1.9.0rc1+incubating-bin.tar.gz
> >>>>>>>>> pip install /tmp/apache-airflow.tar.gz
> >>>>>>>>>
> >>>>>>>>> The steps of updating, are in the UPDATING.md:
> >>>>>>>>> https://github.com/apache/incubator-airflow/blob/master/
> >>>> UPDATING.md
> >>>>>>>>>
> >>>>>>>>> Please note that 1.9 is not released yet, but you are welcome to
> >>>> try
> >>>>>> out
> >>>>>>>>> RC1.
> >>>>>>>>>
> >>>>>>>>> Cheers, Fokko
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
Re: [CANCEL][VOTE] Airflow 1.9.0rc1
Posted by Bolke de Bruin <bd...@gmail.com>.
Hi Chris,
It seems that all of them are merged into the 1.9.0-stable branch, except for one that is only committed to master.
Can we get RC2 out?
Bolke
Sent from my iPhone
> On 10 Nov 2017, at 17:27, Chris Riccomini <cr...@apache.org> wrote:
>
> Hey all,
>
> I'm going to cancel the RC1 vote due to the -1's. I'm tracking the
> following issues for RC2:
>
> 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-1787
> https://issues.apache.org/jira/browse/AIRFLOW-1102
>
> Cheers,
> Chris
>
> On Fri, Nov 10, 2017 at 1:25 AM, Ash Berlin-Taylor <
> ash_airflowlist@firemirror.com> wrote:
>
>> The other difference is that if you depend upon airflow in a module where
>> you want to put it in the install_requires section of a setup.py (not an
>> application which has a requirements.txt, say) you can't use a git tag. Or
>> at least I couldn't get it working.
>>
>> It doesn't make a difference a lot of time, but it is occasionally useful.
>>
>> -ash
>>
>>> On 9 Nov 2017, at 23:08, Alek Storm <al...@gmail.com> wrote:
>>>
>>> It’s not a major difference, but installing from a git repo via pip
>>> requires a completely different syntax, which complicates our tooling,
>> e.g.:
>>>
>>> $ pip install 'apache-airflow[postgres,celery,rabbitmq]=={{version}}'
>>>
>>> $ pip install 'git+git://github.com/apache/
>> incubator-airflow@{{version}}#egg=apache-airflow[postgres,celery,rabbitmq]
>> '
>>>
>>> Alek
>>>
>>>
>>> On Thu, Nov 9, 2017 at 3:53 PM, Arthur Wiedmer <arthur.wiedmer@gmail.com
>>>
>>> wrote:
>>>
>>>> I agree with Bolke that it would be better to provide dev releases in
>> PyPI,
>>>> but my understanding was that, while not an official release channel, it
>>>> still has the apache branding and we should be careful nonetheless.
>>>>
>>>> I am still confused as to why installing from a git tag or the like is
>> not
>>>> OK for testing, provided our release artifact creation process is
>>>> consistent.
>>>>
>>>> Best,
>>>> Arthur
>>>>
>>>> On Thu, Nov 9, 2017 at 12:09 PM, Daniel Huang <dx...@gmail.com>
>> wrote:
>>>>
>>>>> This is how pip handles RC/beta versions:
>>>>>
>>>>>
>>>>>> Pre-release Versions
>>>>>> Starting with v1.4, pip will only install stable versions as specified
>>>> by
>>>>>> PEP426 by default. If a version cannot be parsed as a compliant PEP426
>>>>>> version then it is assumed to be a pre-release.
>>>>>> If a Requirement specifier includes a pre-release or development
>>>> version
>>>>>> (e.g. >=0.0.dev0) then pip will allow pre-release and development
>>>>> versions
>>>>>> for that requirement. This does not include the != flag.
>>>>>> The pip install command also supports a --pre flag that will enable
>>>>>> installing pre-releases and development releases.
>>>>>
>>>>>
>>>>> Source:
>>>>> https://pip.pypa.io/en/stable/reference/pip_install/#pre-
>>>> release-versions
>>>>> <https://pip.pypa.io/en/stable/reference/pip_install/#
>>>> pre-release-versions
>>>>>>
>>>>>
>>>>> On Thu, Nov 9, 2017 at 11:54 AM, Bolke de Bruin <bd...@gmail.com>
>>>> wrote:
>>>>>
>>>>>> I think we should put this up for discussion. PyPi is not an official
>>>>>> apache channel, so in theory we could put anything on PyPI. I also
>>>> think
>>>>>> (didn’t confirm) pip doesn’t upgrade to RC/beta etc.
>>>>>>
>>>>>> Any thoughts?
>>>>>>
>>>>>> Bolke.
>>>>>>
>>>>>>> On 9 Nov 2017, at 15:53, Arthur Wiedmer <ar...@apache.org> wrote:
>>>>>>>
>>>>>>> Hi Alek,
>>>>>>>
>>>>>>> Technically, we cannot release a distribution on PyPI until we have
>>>>> voted
>>>>>>> on a release. And here usually a release artifact. It is a little
>>>>>>> convoluted in the case of Python, but we are getting the hang of it.
>>>>>>>
>>>>>>> That said, installing from a git reference is a possibility too if
>>>> you
>>>>>> want
>>>>>>> the fastest path to install.
>>>>>>>
>>>>>>> Best,
>>>>>>> Arthur
>>>>>>>
>>>>>>> On Nov 9, 2017 06:34, "Alek Storm" <al...@gmail.com> wrote:
>>>>>>>
>>>>>>> I think this has been mentioned before, but it would be much easier
>>>> for
>>>>>> us
>>>>>>> (my team) to test RCs if they were published to PyPI. Or is that
>>>>> against
>>>>>>> Apache guidelines?
>>>>>>>
>>>>>>> Alek
>>>>>>>
>>>>>>> On Thu, Nov 9, 2017 at 8:29 AM, Michael Crawford <
>>>>>>> michael.crawford@modernizingmedicine.com> wrote:
>>>>>>>
>>>>>>>> Thanks. Yes I understand it isn’t released yet.
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 9, 2017, at 9:09 AM, Driesprong, Fokko <fokko@driesprong.frl
>>>>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Michael,
>>>>>>>>>
>>>>>>>>> You have to install it from the tar.gz:
>>>>>>>>>
>>>>>>>>> wget
>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.
>>>>>>>> 9.0rc1/apache-airflow-1.9.0rc1+incubating-bin.tar.gz
>>>>>>>>> pip install /tmp/apache-airflow.tar.gz
>>>>>>>>>
>>>>>>>>> The steps of updating, are in the UPDATING.md:
>>>>>>>>> https://github.com/apache/incubator-airflow/blob/master/
>>>> UPDATING.md
>>>>>>>>>
>>>>>>>>> Please note that 1.9 is not released yet, but you are welcome to
>>>> try
>>>>>> out
>>>>>>>>> RC1.
>>>>>>>>>
>>>>>>>>> Cheers, Fokko
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>