Hello all, We have several workstreams[1] that still need owners. This is a fantastic opportunity for you to take ownership of a key part of Airflow 3 and make a bigger impact. I have also added those items to this meta GitHub issue [2] for easy reference.
Airflow 3 is set to bring numerous improvements and new features, and your contributions can help deliver tons of value to the broader Data Community. Many of these tasks do not require Airflow Improvement Proposals (AIPs), so the August 1st cutoff does not apply. However, if we do not get owners soon, we may consider these tasks for Airflow >= 3.1. On the other hand, if you identify items that aren't AIP worthy but need breaking changes, please create a detailed GitHub issue if it doesn't exist and add "airflow3.0:candidate" label [3][4]. To be clear, this doesn't guarantee that someone will work on it, the best chance to get those items would be for you to help contribute it. Once Airflow 2.10 is released in August, the main branch will become Airflow 3 and we will start accepting breaking changes. We will continue to use Confluence [5][6] to track items and progress on a high level and use GitHub issues to seek help from the community on individual smaller items. Regards, Kaxil [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3+Workstreams#Airflow3Workstreams-Othercandidates [2] https://github.com/apache/airflow/issues/39593 [3] https://github.com/apache/airflow/issues?q=is%3Aopen+label%3Aairflow3.0%3Acandidate+no%3Aassignee+ [4] https://github.com/apache/airflow/labels/airflow3.0%3Acandidate [5] https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3+Workstreams#Airflow3Workstreams-3.0 [6] https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.0
