Thanks Ash. Then it makes sense to me. wt., 18 lut 2025, 13:51 użytkownik Ash Berlin-Taylor <a...@apache.org> napisał:
> This is only talking about the main branch and Airflow 3.0, Airflow 2 is > already branched off and that UI won’t be removed in 2.x at all. > > > On 18 Feb 2025, at 11:54, Michał Modras <michalmod...@google.com.INVALID> > wrote: > > > > Would removing it imply that there's not going to be Airflow 2.12 for > sure? > > Do we want to limit ourselves this way? > > > > On Tue, Feb 18, 2025 at 12:35 PM Abhishek Bhakat > > <abhishek.bha...@astronomer.io.invalid> wrote: > > > >> Where do I find the docs for plugins with the new web UI alternative > for < > >> > >> > https://airflow.apache.org/docs/apache-airflow/stable/howto/custom-view-plugin.html > >>> ? > >> Read the AIP-68 (plugin interface), but is it in a ready state yet. > >> > >> - Avi > >> > >> On Tue, Feb 18, 2025 at 5:26 AM Ankit Chaurasia <sunank...@gmail.com> > >> wrote: > >> > >>> +1 > >>> > >>> Now is the ideal time to make the new UI the default. The old UI has > >>> several issues that we won't be fixing. Transitioning to the new UI > will > >>> encourage users to engage with it more actively and will provide an > >>> excellent opportunity to identify and address any existing gaps. > >>> > >>> *Ankit Chaurasia* > >>> > >>> > >>> > >>> > >>> > >>> > >>> On Tue, Feb 18, 2025 at 10:35 AM Rahul Vats <rah.sharm...@gmail.com> > >>> wrote: > >>> > >>>> +1 for this! The new UI is the way to go, and as more people start > >> using > >>>> it, it provides a great opportunity to identify and address any > >> existing > >>>> gaps. > >>>> > >>>> Regards, > >>>> Rahul Vats > >>>> 9953794332 > >>>> > >>>> On Tue, 18 Feb 2025 at 09:41, Amogh Desai <amoghdesai....@gmail.com> > >>>> wrote: > >>>> > >>>>> Big +1!! > >>>>> > >>>>> It is not easy to maintain the old UI with the rapid development > >> going > >>> on > >>>>> with the new and it only makes little sense to do so. I have also > >> been > >>>>> hitting > >>>>> some strange issues with the old UI and took that as a sign to use > >> the > >>>> new > >>>>> one. Also, using the new UI will require a bit of unlearning from the > >>> old > >>>>> UI > >>>>> which will take some time and it shouldn't come as a surprise to > >> users. > >>>>> Therefore, I think now's the right time, given now is atleast after > >> all > >>>> the > >>>>> alphas. > >>>>> > >>>>> Thanks & Regards, > >>>>> Amogh Desai > >>>>> > >>>>> > >>>>> On Tue, Feb 18, 2025 at 8:25 AM Wei Lee <weilee...@gmail.com> wrote: > >>>>> > >>>>>> +1 for this! And now is the best time. > >>>>>> > >>>>>> I'm not sure whether folks are comfortable with something not > >> working > >>>> on > >>>>>> the new UI for now, though 🤔 (but there are also things breaking > >> in > >>>> the > >>>>>> old UI that we won't fix anyway). Even if we decide to keep the old > >>> UI > >>>>> for > >>>>>> one or two alpha/beta releases, I think it's time (the next release > >>> or > >>>>>> main) to default to the new UI so people can get used to it. > >>>>>> > >>>>>> Best, > >>>>>> Wei > >>>>>> > >>>>>>> On Feb 18, 2025, at 10:29 AM, Jed Cunningham < > >>>> jedcunning...@apache.org > >>>>>> > >>>>>> wrote: > >>>>>>> > >>>>>>> Hello everyone! > >>>>>>> > >>>>>>> As we gear up for the Airflow 3 release, I’d like to kick off a > >>>>>> discussion > >>>>>>> about the timing of removing the old FAB-based UI from Airflow > >>> core. > >>>>>> We’ve > >>>>>>> been investing in the React-based UI for a while now, and I know > >>> that > >>>>> we > >>>>>>> have made tremendous progress on this. > >>>>>>> > >>>>>>> The FAB UI removal is an exciting moment and one we’ve been > >> working > >>>>>> towards > >>>>>>> with AIP-38 (Modern UI) > >>>>>>> < > >>>>>> > >>>>> > >>>> > >>> > >> > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-38+Modern+Web+Application > >>>>>>> > >>>>>>> and its sub-AIPs AIP-68 (plugin interface) > >>>>>>> < > >>>>>> > >>>>> > >>>> > >>> > >> > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-68+Extended+Plugin+Interface+for+React+Views > >>>>>>> , > >>>>>>> AIP-79 (Remove FAB as core dependency) > >>>>>>> < > >>>>>> > >>>>> > >>>> > >>> > >> > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-79%3A+Remove+Flask+AppBuilder+as+Core+dependency > >>>>>>> , > >>>>>>> and AIP-84 (UI REST API) > >>>>>>> < > >>>>> > >> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-84+UI+REST+API > >>>> > >>>>>> - > >>>>>>> removing the FAB UI is a “when”, not an “if”, and I feel the when > >>> is > >>>>> now. > >>>>>>> > >>>>>>> Why now though? > >>>>>>> > >>>>>>> > >>>>>>> - > >>>>>>> > >>>>>>> We’re at a point where keeping the old UI around is more of a > >>>>> liability > >>>>>>> than a benefit > >>>>>>> - > >>>>>>> > >>>>>>> We have a clear path for the remaining feature gaps > >>>>>>> - > >>>>>>> > >>>>>>> ~2/3 of the way there based on the tracking issue > >>>>>>> <https://github.com/apache/airflow/issues/43712>, > >> connections > >>>>> being > >>>>>>> the biggest remaining gap > >>>>>>> - > >>>>>>> > >>>>>>> Removing it unblocks a lot of cleanup and packaging work > >>>>>>> - > >>>>>>> > >>>>>>> If we want only the new UI for the beta period, now is the time > >>> to > >>>>> move > >>>>>>> > >>>>>>> > >>>>>>> We may not get 100% parity before release, and that’s okay. The > >>>> reality > >>>>>> is > >>>>>>> that supporting two UIs just isn’t sustainable because it splits > >>> our > >>>>>> focus > >>>>>>> and adds maintenance overhead. Committing to a single UI helps > >> us > >>>> move > >>>>>>> forward faster and shows clear community buy-in. > >>>>>>> > >>>>>>> Assuming positive responses, Brent can open a PR doing the delete > >>>>> (that’s > >>>>>>> only fair haha)! > >>>>>>> > >>>>>>> Jed > >>>>>> > >>>>>> > >>>>>> > >> --------------------------------------------------------------------- > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > >>>>>> For additional commands, e-mail: dev-h...@airflow.apache.org > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
