You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Jarek Potiuk <Ja...@polidea.com> on 2020/12/03 17:27:21 UTC
[VOTE] Approach for supported python versions
Hello everyone,
I am casting a vote for our approach to support Python version:
It is following the discussion:
https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
The proposal is:
1. We finish support for python versions when they reach EOL (For python
3.6 it means that we will remove it from being supported on 23.12.2021).
2. The "oldest" supported version of Python as the default (3.6 today and
it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes the
default). "Default" is only meaningful in terms of "smoke tests" in CI PRs
which are run using this default version.
3. We support a new version of Python after it is officially released, as
soon as we manage to make it work in our CI pipeline (which might not be
immediate).
The vote will last till Tuesday 8th of December, 6 pm CET.
Consider this my +1 (binding) vote.
The vote follows the "Procedural" voting process
https://www.apache.org/foundation/voting.html - everyone is encouraged to
vote, commiters have binding votes.
J.
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [VOTE] Approach for supported python versions
Posted by Jarek Potiuk <Ja...@polidea.com>.
A bit late, but here is to announce that the vote has passed with 4
binding +1s and 1 non-binding :
Binding votes:
- Jarek Potiuk
- Tomasz Urbaszek
- Deng Xiaodong
- Kaxil Naik
Non-binding votes:
- Darren Weber
I will proceed with updating the docs and clarifying the rule.
J.
On Fri, Dec 4, 2020 at 10:14 AM Tomasz Urbaszek <to...@polidea.com>
wrote:
> +1
>
> On Fri, Dec 4, 2020 at 12:57 AM Darren Weber <dw...@gmail.com>
> wrote:
>
>> +1
>>
>> On Thu, Dec 3, 2020 at 3:23 PM Kaxil Naik <ka...@gmail.com> wrote:
>>
>>> +1
>>>
>>> On Thu, Dec 3, 2020 at 10:14 PM Deng Xiaodong <xd...@gmail.com>
>>> wrote:
>>>
>>>> Yep, it clarifies. I find it important because people may have
>>>> different interpretations on "*support*" and may lead to confusion
>>>> later. But this supplementary statement suffices to make it clear.
>>>>
>>>> So +1 from me for this proposal. Thanks for wrapping this up.
>>>>
>>>>
>>>> XD
>>>>
>>>> On Thu, Dec 3, 2020 at 8:29 PM Jarek Potiuk <Ja...@polidea.com>
>>>> wrote:
>>>>
>>>>> Good point. I propose that we start supporting new python version in
>>>>> master, after CI is working. The new python version will be supported in
>>>>> releases starting from the first major or minor release after that.
>>>>>
>>>>> I hope it clarifies :).
>>>>>
>>>>> J.
>>>>>
>>>>>
>>>>> On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Jarek.
>>>>>>
>>>>>> To clarify on the 3rd point: I assume you meant "*We support a new
>>>>>> version of Python after it is officially released, as soon as we manage to
>>>>>> make it work in our CI pipeline and release a new version of Airflow
>>>>>> (non-Patch version) based on this CI setting-up (which might not be
>>>>>> immediate)*"? Or maybe I misunderstood anything?
>>>>>>
>>>>>>
>>>>>> XD
>>>>>>
>>>>>> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello everyone,
>>>>>>>
>>>>>>> I am casting a vote for our approach to support Python version:
>>>>>>>
>>>>>>> It is following the discussion:
>>>>>>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>>>>>>
>>>>>>> The proposal is:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 1. We finish support for python versions when they reach EOL (For
>>>>>>> python 3.6 it means that we will remove it from being supported on
>>>>>>> 23.12.2021).
>>>>>>>
>>>>>>> 2. The "oldest" supported version of Python as the default (3.6
>>>>>>> today and it will remain the default until 23.12.2021. On 23.12.2021 3.7
>>>>>>> becomes the default). "Default" is only meaningful in terms of "smoke
>>>>>>> tests" in CI PRs which are run using this default version.
>>>>>>>
>>>>>>> 3. We support a new version of Python after it is officially
>>>>>>> released, as soon as we manage to make it work in our CI pipeline (which
>>>>>>> might not be immediate).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>>>>>>
>>>>>>> Consider this my +1 (binding) vote.
>>>>>>>
>>>>>>> The vote follows the "Procedural" voting process
>>>>>>> https://www.apache.org/foundation/voting.html - everyone is
>>>>>>> encouraged to vote, commiters have binding votes.
>>>>>>>
>>>>>>> J.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Jarek Potiuk
>>>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>>>>
>>>>>>> M: +48 660 796 129 <+48660796129>
>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Jarek Potiuk
>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>>
>>>>> M: +48 660 796 129 <+48660796129>
>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>
>>>>>
>
> --
>
> Tomasz Urbaszek
> Polidea <https://www.polidea.com/> | Software Engineer
>
> M: +48 505 628 493 <+48505628493>
> E: tomasz.urbaszek@polidea.com <to...@polidea.com>
>
> Unique Tech
> Check out our projects! <https://www.polidea.com/our-work>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [VOTE] Approach for supported python versions
Posted by Tomasz Urbaszek <to...@polidea.com>.
+1
On Fri, Dec 4, 2020 at 12:57 AM Darren Weber <dw...@gmail.com>
wrote:
> +1
>
> On Thu, Dec 3, 2020 at 3:23 PM Kaxil Naik <ka...@gmail.com> wrote:
>
>> +1
>>
>> On Thu, Dec 3, 2020 at 10:14 PM Deng Xiaodong <xd...@gmail.com>
>> wrote:
>>
>>> Yep, it clarifies. I find it important because people may have different
>>> interpretations on "*support*" and may lead to confusion later. But
>>> this supplementary statement suffices to make it clear.
>>>
>>> So +1 from me for this proposal. Thanks for wrapping this up.
>>>
>>>
>>> XD
>>>
>>> On Thu, Dec 3, 2020 at 8:29 PM Jarek Potiuk <Ja...@polidea.com>
>>> wrote:
>>>
>>>> Good point. I propose that we start supporting new python version in
>>>> master, after CI is working. The new python version will be supported in
>>>> releases starting from the first major or minor release after that.
>>>>
>>>> I hope it clarifies :).
>>>>
>>>> J.
>>>>
>>>>
>>>> On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Jarek.
>>>>>
>>>>> To clarify on the 3rd point: I assume you meant "*We support a new
>>>>> version of Python after it is officially released, as soon as we manage to
>>>>> make it work in our CI pipeline and release a new version of Airflow
>>>>> (non-Patch version) based on this CI setting-up (which might not be
>>>>> immediate)*"? Or maybe I misunderstood anything?
>>>>>
>>>>>
>>>>> XD
>>>>>
>>>>> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
>>>>> wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>>
>>>>>> I am casting a vote for our approach to support Python version:
>>>>>>
>>>>>> It is following the discussion:
>>>>>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>>>>>
>>>>>> The proposal is:
>>>>>>
>>>>>>
>>>>>>
>>>>>> 1. We finish support for python versions when they reach EOL (For
>>>>>> python 3.6 it means that we will remove it from being supported on
>>>>>> 23.12.2021).
>>>>>>
>>>>>> 2. The "oldest" supported version of Python as the default (3.6 today
>>>>>> and it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes
>>>>>> the default). "Default" is only meaningful in terms of "smoke tests" in CI
>>>>>> PRs which are run using this default version.
>>>>>>
>>>>>> 3. We support a new version of Python after it is officially
>>>>>> released, as soon as we manage to make it work in our CI pipeline (which
>>>>>> might not be immediate).
>>>>>>
>>>>>>
>>>>>>
>>>>>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>>>>>
>>>>>> Consider this my +1 (binding) vote.
>>>>>>
>>>>>> The vote follows the "Procedural" voting process
>>>>>> https://www.apache.org/foundation/voting.html - everyone is
>>>>>> encouraged to vote, commiters have binding votes.
>>>>>>
>>>>>> J.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Jarek Potiuk
>>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>>>
>>>>>> M: +48 660 796 129 <+48660796129>
>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>
>>>>>>
>>>>
>>>> --
>>>>
>>>> Jarek Potiuk
>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>
>>>> M: +48 660 796 129 <+48660796129>
>>>> [image: Polidea] <https://www.polidea.com/>
>>>>
>>>>
--
Tomasz Urbaszek
Polidea <https://www.polidea.com/> | Software Engineer
M: +48 505 628 493 <+48505628493>
E: tomasz.urbaszek@polidea.com <to...@polidea.com>
Unique Tech
Check out our projects! <https://www.polidea.com/our-work>
Re: [VOTE] Approach for supported python versions
Posted by Darren Weber <dw...@gmail.com>.
+1
On Thu, Dec 3, 2020 at 3:23 PM Kaxil Naik <ka...@gmail.com> wrote:
> +1
>
> On Thu, Dec 3, 2020 at 10:14 PM Deng Xiaodong <xd...@gmail.com> wrote:
>
>> Yep, it clarifies. I find it important because people may have different
>> interpretations on "*support*" and may lead to confusion later. But this
>> supplementary statement suffices to make it clear.
>>
>> So +1 from me for this proposal. Thanks for wrapping this up.
>>
>>
>> XD
>>
>> On Thu, Dec 3, 2020 at 8:29 PM Jarek Potiuk <Ja...@polidea.com>
>> wrote:
>>
>>> Good point. I propose that we start supporting new python version in
>>> master, after CI is working. The new python version will be supported in
>>> releases starting from the first major or minor release after that.
>>>
>>> I hope it clarifies :).
>>>
>>> J.
>>>
>>>
>>> On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com>
>>> wrote:
>>>
>>>> Thanks Jarek.
>>>>
>>>> To clarify on the 3rd point: I assume you meant "*We support a new
>>>> version of Python after it is officially released, as soon as we manage to
>>>> make it work in our CI pipeline and release a new version of Airflow
>>>> (non-Patch version) based on this CI setting-up (which might not be
>>>> immediate)*"? Or maybe I misunderstood anything?
>>>>
>>>>
>>>> XD
>>>>
>>>> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
>>>> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I am casting a vote for our approach to support Python version:
>>>>>
>>>>> It is following the discussion:
>>>>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>>>>
>>>>> The proposal is:
>>>>>
>>>>>
>>>>>
>>>>> 1. We finish support for python versions when they reach EOL (For
>>>>> python 3.6 it means that we will remove it from being supported on
>>>>> 23.12.2021).
>>>>>
>>>>> 2. The "oldest" supported version of Python as the default (3.6 today
>>>>> and it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes
>>>>> the default). "Default" is only meaningful in terms of "smoke tests" in CI
>>>>> PRs which are run using this default version.
>>>>>
>>>>> 3. We support a new version of Python after it is officially released,
>>>>> as soon as we manage to make it work in our CI pipeline (which might not be
>>>>> immediate).
>>>>>
>>>>>
>>>>>
>>>>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>>>>
>>>>> Consider this my +1 (binding) vote.
>>>>>
>>>>> The vote follows the "Procedural" voting process
>>>>> https://www.apache.org/foundation/voting.html - everyone is
>>>>> encouraged to vote, commiters have binding votes.
>>>>>
>>>>> J.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Jarek Potiuk
>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>>
>>>>> M: +48 660 796 129 <+48660796129>
>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>
>>>>>
>>>
>>> --
>>>
>>> Jarek Potiuk
>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>
>>> M: +48 660 796 129 <+48660796129>
>>> [image: Polidea] <https://www.polidea.com/>
>>>
>>>
Re: [VOTE] Approach for supported python versions
Posted by Kaxil Naik <ka...@gmail.com>.
+1
On Thu, Dec 3, 2020 at 10:14 PM Deng Xiaodong <xd...@gmail.com> wrote:
> Yep, it clarifies. I find it important because people may have different
> interpretations on "*support*" and may lead to confusion later. But this
> supplementary statement suffices to make it clear.
>
> So +1 from me for this proposal. Thanks for wrapping this up.
>
>
> XD
>
> On Thu, Dec 3, 2020 at 8:29 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
>> Good point. I propose that we start supporting new python version in
>> master, after CI is working. The new python version will be supported in
>> releases starting from the first major or minor release after that.
>>
>> I hope it clarifies :).
>>
>> J.
>>
>>
>> On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com> wrote:
>>
>>> Thanks Jarek.
>>>
>>> To clarify on the 3rd point: I assume you meant "*We support a new
>>> version of Python after it is officially released, as soon as we manage to
>>> make it work in our CI pipeline and release a new version of Airflow
>>> (non-Patch version) based on this CI setting-up (which might not be
>>> immediate)*"? Or maybe I misunderstood anything?
>>>
>>>
>>> XD
>>>
>>> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
>>> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I am casting a vote for our approach to support Python version:
>>>>
>>>> It is following the discussion:
>>>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>>>
>>>> The proposal is:
>>>>
>>>>
>>>>
>>>> 1. We finish support for python versions when they reach EOL (For
>>>> python 3.6 it means that we will remove it from being supported on
>>>> 23.12.2021).
>>>>
>>>> 2. The "oldest" supported version of Python as the default (3.6 today
>>>> and it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes
>>>> the default). "Default" is only meaningful in terms of "smoke tests" in CI
>>>> PRs which are run using this default version.
>>>>
>>>> 3. We support a new version of Python after it is officially released,
>>>> as soon as we manage to make it work in our CI pipeline (which might not be
>>>> immediate).
>>>>
>>>>
>>>>
>>>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>>>
>>>> Consider this my +1 (binding) vote.
>>>>
>>>> The vote follows the "Procedural" voting process
>>>> https://www.apache.org/foundation/voting.html - everyone is encouraged
>>>> to vote, commiters have binding votes.
>>>>
>>>> J.
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Jarek Potiuk
>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>>
>>>> M: +48 660 796 129 <+48660796129>
>>>> [image: Polidea] <https://www.polidea.com/>
>>>>
>>>>
>>
>> --
>>
>> Jarek Potiuk
>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>
>> M: +48 660 796 129 <+48660796129>
>> [image: Polidea] <https://www.polidea.com/>
>>
>>
Re: [VOTE] Approach for supported python versions
Posted by Deng Xiaodong <xd...@gmail.com>.
Yep, it clarifies. I find it important because people may have different
interpretations on "*support*" and may lead to confusion later. But this
supplementary statement suffices to make it clear.
So +1 from me for this proposal. Thanks for wrapping this up.
XD
On Thu, Dec 3, 2020 at 8:29 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Good point. I propose that we start supporting new python version in
> master, after CI is working. The new python version will be supported in
> releases starting from the first major or minor release after that.
>
> I hope it clarifies :).
>
> J.
>
>
> On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com> wrote:
>
>> Thanks Jarek.
>>
>> To clarify on the 3rd point: I assume you meant "*We support a new
>> version of Python after it is officially released, as soon as we manage to
>> make it work in our CI pipeline and release a new version of Airflow
>> (non-Patch version) based on this CI setting-up (which might not be
>> immediate)*"? Or maybe I misunderstood anything?
>>
>>
>> XD
>>
>> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> I am casting a vote for our approach to support Python version:
>>>
>>> It is following the discussion:
>>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>>
>>> The proposal is:
>>>
>>>
>>>
>>> 1. We finish support for python versions when they reach EOL (For python
>>> 3.6 it means that we will remove it from being supported on 23.12.2021).
>>>
>>> 2. The "oldest" supported version of Python as the default (3.6 today
>>> and it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes
>>> the default). "Default" is only meaningful in terms of "smoke tests" in CI
>>> PRs which are run using this default version.
>>>
>>> 3. We support a new version of Python after it is officially released,
>>> as soon as we manage to make it work in our CI pipeline (which might not be
>>> immediate).
>>>
>>>
>>>
>>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>>
>>> Consider this my +1 (binding) vote.
>>>
>>> The vote follows the "Procedural" voting process
>>> https://www.apache.org/foundation/voting.html - everyone is encouraged
>>> to vote, commiters have binding votes.
>>>
>>> J.
>>>
>>>
>>>
>>> --
>>>
>>> Jarek Potiuk
>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>
>>> M: +48 660 796 129 <+48660796129>
>>> [image: Polidea] <https://www.polidea.com/>
>>>
>>>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>
Re: [VOTE] Approach for supported python versions
Posted by Jarek Potiuk <Ja...@polidea.com>.
Good point. I propose that we start supporting new python version in
master, after CI is working. The new python version will be supported in
releases starting from the first major or minor release after that.
I hope it clarifies :).
J.
On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong <xd...@gmail.com> wrote:
> Thanks Jarek.
>
> To clarify on the 3rd point: I assume you meant "*We support a new
> version of Python after it is officially released, as soon as we manage to
> make it work in our CI pipeline and release a new version of Airflow
> (non-Patch version) based on this CI setting-up (which might not be
> immediate)*"? Or maybe I misunderstood anything?
>
>
> XD
>
> On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
>> Hello everyone,
>>
>> I am casting a vote for our approach to support Python version:
>>
>> It is following the discussion:
>> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>>
>> The proposal is:
>>
>>
>>
>> 1. We finish support for python versions when they reach EOL (For python
>> 3.6 it means that we will remove it from being supported on 23.12.2021).
>>
>> 2. The "oldest" supported version of Python as the default (3.6 today and
>> it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes the
>> default). "Default" is only meaningful in terms of "smoke tests" in CI PRs
>> which are run using this default version.
>>
>> 3. We support a new version of Python after it is officially released, as
>> soon as we manage to make it work in our CI pipeline (which might not be
>> immediate).
>>
>>
>>
>> The vote will last till Tuesday 8th of December, 6 pm CET.
>>
>> Consider this my +1 (binding) vote.
>>
>> The vote follows the "Procedural" voting process
>> https://www.apache.org/foundation/voting.html - everyone is encouraged
>> to vote, commiters have binding votes.
>>
>> J.
>>
>>
>>
>> --
>>
>> Jarek Potiuk
>> Polidea <https://www.polidea.com/> | Principal Software Engineer
>>
>> M: +48 660 796 129 <+48660796129>
>> [image: Polidea] <https://www.polidea.com/>
>>
>>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [VOTE] Approach for supported python versions
Posted by Deng Xiaodong <xd...@gmail.com>.
Thanks Jarek.
To clarify on the 3rd point: I assume you meant "*We support a new version
of Python after it is officially released, as soon as we manage to make it
work in our CI pipeline and release a new version of Airflow (non-Patch
version) based on this CI setting-up (which might not be immediate)*"? Or
maybe I misunderstood anything?
XD
On Thu, Dec 3, 2020 at 6:27 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Hello everyone,
>
> I am casting a vote for our approach to support Python version:
>
> It is following the discussion:
> https://lists.apache.org/thread.html/r57502b89f66689a2e5e061ae28ef2ceb8ba7f5cd921ac34b2f7ebe96%40%3Cdev.airflow.apache.org%3E
>
> The proposal is:
>
>
>
> 1. We finish support for python versions when they reach EOL (For python
> 3.6 it means that we will remove it from being supported on 23.12.2021).
>
> 2. The "oldest" supported version of Python as the default (3.6 today and
> it will remain the default until 23.12.2021. On 23.12.2021 3.7 becomes the
> default). "Default" is only meaningful in terms of "smoke tests" in CI PRs
> which are run using this default version.
>
> 3. We support a new version of Python after it is officially released, as
> soon as we manage to make it work in our CI pipeline (which might not be
> immediate).
>
>
>
> The vote will last till Tuesday 8th of December, 6 pm CET.
>
> Consider this my +1 (binding) vote.
>
> The vote follows the "Procedural" voting process
> https://www.apache.org/foundation/voting.html - everyone is encouraged to
> vote, commiters have binding votes.
>
> J.
>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>