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 <jarek.pot...@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/> > >
