Taragolis commented on code in PR #35376: URL: https://github.com/apache/airflow/pull/35376#discussion_r1380733462
########## README.md: ########## @@ -347,8 +349,8 @@ stable versions - as soon as all Airflow dependencies support building, and we s 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. 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``. +to use ``Debian Bookworm`` in February/March 2022. The version was used in the next MINOR release after +the switch happened. In case of the Bookworm switch - 2.3.0 version used ``Debian Bookworm``. Review Comment: I think we need to change date and version. As well as previous line pointed to Buster (Debian 10) ########## dev/breeze/doc/adr/0004-using-docker-images-as-test-environment.md: ########## @@ -120,7 +120,7 @@ suited for the job: * management and automated synchronisation of the environment can be easily done using simple, external scripts that will check the "freshness" of the images and propose corrective actions (pulling or rebuilding the image) for the user whenever they are needed (all that in cross-platform way) -* we can use specific base image (Debian Bullseye with Long Term Support) and rely on security fixes provided +* we can use specific base image (Debian bookworm with Long Term Support) and rely on security fixes provided Review Comment: Should we use capitalize name for Debian release? E.g. Debian Bookworm. Also it related to the other places -- 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]
