potiuk opened a new pull request #21378:
URL: https://github.com/apache/airflow/pull/21378


   Debian 11 Bullseye have been released some time ago as the new
   LTS Debian release and already all our dependencies (including
   MySQL and MSSQL ODBC drivers) caught up with it so we can finally
   migrate to it.
   
   This change switches base images to bullsey for our Dockerfiles
   as well as for Redis image we are using in CI.
   
   The relevant packages have been updated to include that
   and documentation have been updated.
   
   Examples of ours also are updated to use "bullseye" rather than
   buster.
   
   Closes: #18190
   Closes: #18279
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to