Great work on optimizing the DB migrations Rahul and everyone who helped. On Tue, 24 Mar 2026 at 13:17, Rahul Vats <[email protected]> wrote:
> Dear Airflow Community, > > I am writing to inform you that we are planning to cut the first release > candidate for Apache Airflow 3.2.0 on 30th March(Monday). > > > RELEASE BRANCH UPDATE > ===================== > > The v3-2-test branch is now our official release branch for Airflow 3.2.0. > > Effective immediately: > > - v3-2-test is the release branch for all 3.2.0 releases (beta, RC, and > final) > - I will be manually cherry-picking changes from main to v3-2-test on a > daily basis through RC1 (expected end of next week) > - No new features will be cherry-picked — only critical bug fixes, feature > completion changes and release preparation changes > > > IMPORTANT: Do NOT Cherry-pick Directly > ======================================= > > Please do not cherry-pick any changes to v3-2-test directly, even if you > have permissions to do so. > > Here's why this process is critical: > > 1. Quality Control: Each change needs to be vetted for release stability > 2. Release Notes: All changes must be properly documented in release notes > 3. Test Stability: We need to prevent the test surface from constantly > shifting > > > HOW TO GET CHANGES INTO 3.2.0 > ============================== > > If you have a change that should be included in 3.2.0: > > 1. Merge to main first — ensure it passes all CI checks > 2. Add to 3.2.0 milestone: > https://github.com/apache/airflow/milestone/106 > > > WHAT QUALIFIES FOR CHERRY-PICKING > ================================== > > Will be considered: > - Critical bug fixes affecting core functionality > - Translation updates (if significant) > - Feature completion changes for 3.2 > - Security fixes > - Blocker issues preventing testing > - Documentation corrections for new 3.2.0 features > > > OPEN ISSUES TO PRIORITIZE BEFORE RC1 > ====================================== > > Great news, thanks to the incredible effort from the community, we have > already resolved 19 critical > < > https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aclosed%20label%3Aaffected_version%3A3.2.0beta%20and%20(label%3Apriority%3Ahigh%20OR%20label%3Apriority%3Acritical) > > > and high priority issues from the 3.2.0beta > testing period, including important migration performance issues. This is a > testament to the quality and dedication of our contributors! > > There are currently no critical and high priority open issues remaining > from 3.2.0beta > testing. The only remaining open issues are: > > Medium Priority Issues (3 open): > > https://github.com/apache/airflow/issues?q=is%3Aissue+state%3Aopen+label%3Aaffected_version%3A3.2.0beta+label%3Apriority%3Amedium > > These are non-blocking for RC1 but should be addressed before the final > 3.2.0 release. > > > CALL FOR ACTION > =============== > > If you have been working on any of these issues or have capacity to help, > please: > > 1. Test the 3.2.0b2 against your use cases to identify any > remaining critical issues > 2. Comment on existing issues with additional context, reproduction steps, > or potential solutions > > If any severe blockers are discovered before 30th March(Monday), we may > need to adjust > the timeline. Please raise any critical concerns as soon as possible. > > Thank you for all your contributions and testing efforts with the 3.2.0beta > release. Your feedback has been invaluable in identifying and resolving > issues. > > Looking forward to delivering a solid RC1 for the community! > > Best regards, > Rahul Vats >
