Impressive!
Thanks Jarek.
On Thu, Sep 5, 2024 at 3:26 PM Jarek Potiuk wrote:
> Created an issue in CI/CD project describing what would need to be done to
> have CI/CD automation in place for it:
> https://github.com/apache/airflow/issues/42031 - should be very easy.
>
> On Thu, Sep 5, 2024 at 2
Created an issue in CI/CD project describing what would need to be done to
have CI/CD automation in place for it:
https://github.com/apache/airflow/issues/42031 - should be very easy.
On Thu, Sep 5, 2024 at 2:46 PM Jarek Potiuk wrote:
> Labels are cool Indeed.
>
> Automated test is not too diffi
Thanks Brent.
Yes I like the idea of labels, I believe this will help reviewers know that
they have to pay extra attention because specific rules apply to updating
the legacy-ui/api during airflow 3 development.
An automated test is even better but might be more effort to develop.
On Wed, Sep 4,
I like the plan in its entirety.
Some technicalities - likely we do not want to automate what is / is not
allowed - managing it might be difficult, but we could as well add some
separate non-critical / failing test that will "fail" when the "old" area
is touched in the PR (but it could be very cle
Hi all,
As part of AIPs 38, 79 and 84, Pierre and I have started a new API based on
FastAPI and a new UI based purely off of React. The current UI, rest API
and webserver endpoints will now be considered "legacy" and will be
completely removed by the time Airflow 3.0 is released. But there will be
