potiuk commented on code in PR #35376: URL: https://github.com/apache/airflow/pull/35376#discussion_r1381310788
########## README.md: ########## @@ -344,20 +346,21 @@ we publish an Apache Airflow release. Those images contain: The version of the base OS image is the stable version of Debian. Airflow supports using all currently active stable versions - as soon as all Airflow dependencies support building, and we set up the CI pipeline for -building and testing the OS version. Approximately 6 months before the end-of-life of a previous stable -version of the OS, Airflow switches the images released to use the latest supported version of the OS. +building and testing the OS version. Approximately 6 months before the end-of-regular support of a +previous stable version of the OS, Airflow switches the images released to use the latest supported +version of the OS. + For example since ``Debian Buster`` end-of-life was August 2022, Airflow switched the images in `main` branch to use ``Debian Bullseye`` in February/March 2022. The version was used in the next MINOR release after the switch happened. In case of the Bullseye switch - 2.3.0 version used ``Debian Bullseye``. The images released in the previous MINOR version continue to use the version that all other releases -for the MINOR version used. - -Support for ``Debian Buster`` image was dropped in August 2022 completely and everyone is expected to -stop building their images using ``Debian Buster``. +for the MINOR version used. Similar switch from ``Debian Bullseye`` to ``Debian Bookworm`` has been implemented +before 2.8.0 release in October 2023 and ``Debian Bookworm`` will be the only option supported as of Review Comment: We switch before 2.8.0 in main. See also the recent description I added explaining the `main` == NEXT_MINOR RELEASE approach https://github.com/apache/airflow/blob/main/README.md#what-goes-into-the-next-release Basically everything merged to main is aimed to be released in the next MINOR - (and some of it is cherry-picked to v2-CURRENT_MINOR to be part of next 2.CURRENT_MINOR.patchlevel . So merging it to main BEFORE we cut-off v2-8 branch means that it is targetted for 2.8.0 release. -- 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]
