+1, burn it down. You folks have put so much work into the new UI, I'm sure it will be good to see it get its due attention from the users and this feels like the perfect time.
- ferruzzi ________________________________ From: Karthikeyan <tir.kar...@gmail.com> Sent: Tuesday, February 18, 2025 8:51 AM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSS] Time to say goodbye to the old UI? CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. +1 on making the new UI by default as soon as possible since there will be more feedback and testing. The old UI features can be ported unless a blocker similar to how the Airflow 2 UI itself was ported to React incrementally in each release from Flask templates. Airflow 3 UI in React and Chakra 3 was also great to contribute compared to the Airflow 2 UI which was a mix of js/ts and html files. Authentication and authorization from UI IMO are the blocker issues and it will be good to have them tested for sometime before release to ensure there are no security issues. Since Airflow 3 UI will be a change of muscle memory for more users it will be good to have some walkthroughs and docs. Webapps that have product walkthroughs to introduce new features can be good to have. I did some work initially as PoC last year but it got lost in the changes to the UI. https://github.com/tirkarthi/airflow/tree/joyride-demo https://react-joyride.com/ On Tue, Feb 18, 2025 at 9:21 PM 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 > > -- Regards, Karthikeyan S
