Hi Vincent, Thanks for sharing the test plan. I have added this to the 3.2 test plan. <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.2+Test+Plan>
Best regards, Rahul Vats On Sat, 21 Feb 2026 at 14:19, Srabasti Banerjee < [email protected]> wrote: > Hello Vincent, > > Thanks for sharing the contribution opportunity! > > I commented on [Multi-team] [Testing] Team management #62243 > <https://github.com/apache/airflow/issues/62243> and shared results of > testing carried out so far. > > Appreciate if you could assign it to me. > > Warm Regards, > Srabasti Banerjee > > On Fri, Feb 20, 2026 at 1:08 PM Vincent Beck <[email protected]> wrote: > > > Hi everyone, > > > > As you may know, the multi-team feature will be introduced as an > > experimental feature in the upcoming 3.2 release of Apache Airflow. > > > > This feature is marked as experimental for two main reasons. First, while > > the core implementation is in place, we want to validate its behavior > > across a wide range of real-world environments. Second, the feature is > not > > yet complete: some capabilities are still missing and will be added > > incrementally based on feedback and identified needs. > > > > To support this effort, we’ve prepared a test plan available here: > > https://github.com/orgs/apache/projects/577/views/1 > > > > We would greatly appreciate your help in testing it. Every Airflow > > environment is unique, and ensuring the feature works reliably across > > different setups and configurations requires lots of people :) > > > > How to help? > > > > To make testing more effective and avoid duplication of effort, we > suggest > > the following workflow: > > > > 1. Pick a task from the test plan. > > 2. Before starting, leave a comment on the task to indicate that you’re > > beginning testing. > > 3. Try to select a task that doesn’t already have someone actively > working > > on it. > > 4. Once you’re done, comment on the task with your results, findings, or > > any issues you encountered. > > > > The test plan is intended as a set of guidelines to make validation > easier > > and more structured. That said, if you believe certain scenarios or tests > > are missing, please feel free to run them anyway and share your feedback. > > > > Thank you in advance for your time, testing, and feedback. > > > > Vincent > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
