Huge +1000. NOW! 3 (and even 4) reasons :
* The sooner we do it, the better, It's been holding us back and making quite a few things more difficult. I had to - for example - fix quite a few tests when moving stuff around and with more moves coming, this one will make our lives easier. I even removed one or two, knowing they will anyhow be removed if they turned out to be difficult to fix in anticipation of this removal (yes I was cheating a bit, I know) * Removing the UI will unblock final discussion and decision on airflow packaging. Before we do it, it's unclear what will be the layout of dependencies and cross-dependencies between packages, we were unsure for example if it makes sense to treat scheduler and web-server as two different distributions - and we will really see it after removing the old UI. * What Vikram wrote - removal of the old ui will mean more eyes and hands looking for bugs (and possibly fixing them) And finally the 4th reason - while I am not very fond of Cortés as a person for what he did - but - yes, he burned the ships when they landed in South America, and it did change the world [1]. So ... time to burn the ships .... Hernán er. Brent. [1] https://onepeterfive.com/burn-ships-hernan-cortes-new-world/ J. On Tue, Feb 18, 2025 at 5:19 PM 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. > > >
