I guess it wasn't quite clear what "finish" means, particularly how it
interacts with SemVer and Airflow releases.
Lets take Python 3.6 as a concrete example -- it is end of life at the
end of this year, 23rd Dec, 202 1 <<https://endoflife.date/python>>
Does dropping support for Python 3.6, even if it is not supported count
as a breaking change to Airflow, needing a 3.0?
-ash
On Tue, 13 Apr, 2021 at 19:44, Jarek Potiuk <[email protected]> wrote:
On Tue, Apr 13, 2021 at 2:35 PM Ash Berlin-Taylor <[email protected]
<mailto:[email protected]>> wrote:
This sounds good to me.
The next question this leads me to is: when do we _drop_ support for
a version of Python or Kubernetes?
I believe that's the first point in the proposal ("finish" = "drop").
If that's not clear, I will change it to drop
Or maybe you mean some other form of "dropping support?
1. We finish support for Python and K8S versions when they reach
EOL (For Python
3.6 it means that we will remove it from being supported on
23.12.2021, for K8S
the 1.19 version supports end in September 2021).
--
+48 660 796 129
