+1 I completely agree that now is the right time to remove the old UI.
Keeping both UIs around at this stage is more of a drag than a safety net and is increasing the maintenance cost (things are starting to become very wonky in the old UI). Having a clean break sets clear expectations: Airflow 3 is moving forward with the React UI, and that's where we should be focusing our energy. Excited to see this happen! On Tue, Feb 18, 2025 at 11:20 AM Brent Bovenzi <br...@astronomer.io.invalid> wrote: > +1 > > - We absolutely don't want to have the old UI when 3.0 launches. > - It's a big change that can't wait until the last minute > - There are enough changes in main that the old UI is now breaking > > Please check out our UI meta issue > <https://github.com/apache/airflow/issues/43712>for getting to feature > parity (and beyond!). Leave a comment if there is anything missing. > > > On Tue, Feb 18, 2025 at 9:46 AM Jed Cunningham <jedcunning...@apache.org> > 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. > > >
