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


   In order to switch smoothly to Debian Bullseye we need to run a
   few more tests and see if the performance impact we observe is
   consistent (the tests with Public Runners seems to be killed more
   frequently there).
   
   This requires some preparatory work - namely add the capability
   of overriding the DEBIAN_VERSION via PR - because otherwise
   Build Images workflow that runs from main will build buster images
   until the change is actually merged.
   
   This change introduce this capability without switching to
   Bullseye yet - it will unblock the actual PR that will make the
   change from failing in PRs though.
   
   <!--
   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