Dear Airflowers, I am looking forward to meeting many of you this coming week at the Airflow Summit. It will be wonderful to connect in person after a year of online collaboration since the last Summit.
I’d like to put a proposal in front of all of you. We’re sure to hear valuable feedback from users who have adopted or are adopting Airflow 3. My proposal is that we dedicate October, the four weeks following the Summit, to polishing work rather than new feature development. This would mean focusing on smoothing out any rough edges in the adoption journey and making it easier for users to take full advantage of the new capabilities we’ve released. Depending on the aggregated feedback, we can also consider multiple patch releases during this period to quickly incorporate improvements. As part of this, let's make sure feedback is easy to track: - System of record: Use Github issues <https://github.com/apache/airflow/issues> as the source of truth, even if there is a conversation over slack or on the dev list. - Version labelling: Include the Airflow version so it can be labeled appropriated (label:affected_version either 3.0 or 3.1), easily reproduced and resolved. - Upgrade blockers: Indicate if this affects upgrades from 2.x. We have been labeling and tracking these separately. - Documentation vs. code: Indicate if this is a documentation gap, rather than a code problem. - Context: Airflow's flexibility allows for a wide range of behavior. With Airflow 3's architectural changes, especially the new TaskSDK model, some implicit behaviors may now need to be explicitly specified. If you found anything confusing or frustrating, please let us know if a documentation update, upgrade script change, or a clarifying example would be helpful. We are looking for active participation from everyone, including those who haven't contributed before. Even a small contribution such as a clear reproduction scenario, a documentation improvement, or a simple upgrade script update can make a big difference. Thank you and best regards, Vikram -- Vikram Koka Chief Strategy Officer Email: [email protected] <https://www.astronomer.io/>
