Lazy consensus has passed. Preparation of Fab provider to set next version as major version here: https://github.com/apache/airflow/pull/43939
On 2024/11/07 00:08:14 Jarek Potiuk wrote: > Yeah. That's the best course of action, I think ... > > On Wed, Nov 6, 2024 at 6:55 PM Beck, Vincent <vincb...@amazon.com.invalid> > wrote: > > > Hi Airflow devs, > > > > I am calling a LAZY CONSENSUS to create a new major version of the fab > > provider that will only be compatible with Airflow 3. The reason why we > > need it is we are planning to make some breaking changes in the fab > > provider that will be incompatible with Airflow 2.X. Here are some examples > > of these breaking changes: > > > > * The auth manager interface in core Airflow needs to be modified > > (with breaking changes). Therefore, we need to have a FAB auth manager > > compatible with Airflow 2.X (current provider version) and a FAB auth > > manager compatible with Airflow 3.X (apache-airflow-providers-fab>= 2.0) > > * We want to migrate to SQLAlchemy 2.0. This means some breaking > > changes in fab provider which will be incompatible with Airflow 2.X > > > > Overall, fab provider is tightly coupled with Airflow 2 and its > > dependencies, if we want to make some modifications in this provider > > without causing frictions in Airflow 2.X, having this major version is > > necessary. > > > > If some code changes are required in FAB provider 1.X (compatible with > > Airflow 2.X), we can always branch off from the last fab provider we > > released for 2.X and release minor version there. > > > > If no one objects, this vote will pass 3 days from now, 2pm EST Saturday > > Nov 9, 2024. > > > > Vincent > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
