tiagornandrade commented on issue #41641:
URL: https://github.com/apache/airflow/issues/41641#issuecomment-2704960187
π Airflow 2 β 3 Migration Rules Tracking
Why?
With the introduction of breaking changes in the Apache Airflow main branch,
it is essential to document and organize the rules that can help users migrate
from Airflow 2 to Airflow 3. Automated migration tools can be useful in this
process.
The breaking changes can be found:
β’ In PRs labeled:
[airflow3.0:breaking](https://github.com/apache/airflow/pulls?q=is%3Apr+label%3Aairflow3.0%3Abreaking)
β’ In newsfragments/*.significant.rst files
Tasks
π List all necessary changes
β’ Based on newsfragments/(\d{5}).significant.rst files
β’ Group and organize the rules into sub-issues
π Sub-Issues for Tracking
πΉ Backporting Tools
β’ Backport airflow config lint to Airflow 2.11 - #45632
πΉ Listing and Organizing Rules
β’ Between 44080.significant.rst and 45017.significant.rst
β’ List all relevant rules
β’ Create sub-issues for each rule set
β’ π Airflow 2 β 3 Auto Migration Rules - ruff (44080 ~ 45017)
#45212
β’ π Airflow 2 β 3 Auto Migration Rules - airflow config lint
(44080 ~ 45017) #45213
β’ Before 44080.significant.rst
β’ List all relevant rules
β’ Create sub-issues for each rule set
β’ π Airflow 2 β 3 Auto Migration Rules - ruff (~44080) #44556
β’ π Airflow 2 β 3 Auto Migration Rules - airflow config (~44080)
#44555
π References
β’ π [PRs with breaking
changes](https://github.com/apache/airflow/pulls?q=is%3Apr+label%3Aairflow3.0%3Abreaking)
β’ π newsfragments/*.significant.rst files containing significant
changes
π‘ Next Steps
β’ Create a detailed list of migration rules based on newsfragments
β’ Create specific sub-issues for each rule set
β’ Discuss the best approach for implementing automated migration
rules
β’ Submit a PR to add support for automatic migration
βοΈ I am willing to submit a PR to help with this migration! π
π Community Commitment: I agree to follow the projectβs [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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]