eladkal commented on a change in pull request #17806:
URL: https://github.com/apache/airflow/pull/17806#discussion_r694750361
##########
File path: README.md
##########
@@ -254,44 +252,44 @@ Apache Airflow version life cycle:
| Version | Current Patch/Minor | State | First Release | Limited Support
| EOL/Terminated |
|---------|---------------------|-----------|---------------|-----------------|----------------|
-| 2 | 2.1.3 | Supported | Dec 17, 2020 | Dec 2021
| TBD |
+| 2.0 | 2.1.3 | Supported | Dec 17, 2020 | Dec 31, 2021
| TBD |
Review comment:
The version series is 2 not 2.0
In Airflow 1 - a breaking change could be introduced between 1.x to 1.y
which is why each version is in a separate row.
In Airflow 2 - we changed to
[semver](https://airflow.apache.org/docs/apache-airflow/stable/release-process.html#airflow-s-release-process)
so it doesn't require new row per patch version.
Also I'm not sure if the date for limited support is Dec 31. We don't know
it yet.
##########
File path: README.md
##########
@@ -254,44 +252,44 @@ Apache Airflow version life cycle:
| Version | Current Patch/Minor | State | First Release | Limited Support
| EOL/Terminated |
|---------|---------------------|-----------|---------------|-----------------|----------------|
-| 2 | 2.1.3 | Supported | Dec 17, 2020 | Dec 2021
| TBD |
+| 2.0 | 2.1.3 | Supported | Dec 17, 2020 | Dec 31, 2021
| TBD |
| 1.10 | 1.10.15 | EOL | Aug 27, 2018 | Dec 17, 2020
| June 17, 2021 |
| 1.9 | 1.9.0 | EOL | Jan 03, 2018 | Aug 27, 2018
| Aug 27, 2018 |
| 1.8 | 1.8.2 | EOL | Mar 19, 2017 | Jan 03, 2018
| Jan 03, 2018 |
-| 1.7 | 1.7.1.2 | EOL | Mar 28, 2016 | Mar 19, 2017
| Mar 19, 2017 |
+| 1.7 | 1.7.12 | EOL | Mar 28, 2016 | Mar 19, 2017
| Mar 19, 2017 |
Review comment:
this is wrong. The version is 1.7.1.2
https://airflow.apache.org/announcements/#may-20-2016
https://github.com/apache/airflow/releases/tag/1.7.1.2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
