Thanks for starting this thread, Jed. Around September last year, I was pessimistic about when this would happen. I have been very impressed by our rate of progress on this set of AIPs over the last few months. I see the visible progress even across the alpha releases and am really pleased by where we are today.
Based on that, I am +1 on this. Vikram On Tue, Feb 18, 2025 at 7:51 AM Vincent Beck <vincb...@apache.org> wrote: > HUGE +1! That would have multiple benefits: > - Forcing people to use the new UI will help us to identity bugs/gaps in > the new UI > - There is still quite a bit of code in Airflow codebase (especially in > auth managers) to support old UI. Removing the old UI would allow us to > clean that up > > On 2025/02/18 14:46:24 Jed Cunningham wrote: > > AIP-68 really is about expanding what can be done from a plugin. Main > > already supports fastapi_apps and extra links from plugins. Existing > > plugins using flask_blueprint and appbuilder_views are deprecated but > will > > continue to work with the FAB provider installed (having that > compatibility > > layer is one of the goals of AIP-79). I believe that leaves menu items as > > the only gap. > > > > Either way, we cannot wait until we have 100% parity - that will either > be > > too late before the release date or _after_ 3.0 is already out. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
