+1(binding)
czw., 5 wrz 2024, 08:10 użytkownik Scheffler Jens (XC-AS/EAE-ADA-T)
napisał:
> Hi Kaxil,
>
> +1 binding. With the assumption that AIP-80 was voted I assume we planned
> to introduce the new templating early. This would be (in my eyes except we
> see other things we need to mark depre
+1 (non-binding)
On Thu, Sep 5, 2024 at 10:42 AM Ephraim Anierobi
wrote:
> +1 (binding)
>
> On Thu, 5 Sept 2024 at 08:57, Jarek Potiuk wrote:
>
> > +1(binding)
> >
> > czw., 5 wrz 2024, 08:10 użytkownik Scheffler Jens (XC-AS/EAE-ADA-T)
> > napisał:
> >
> > > Hi Kaxil,
> > >
> > > +1 binding. W
Hello all,
Just a reminder that we will have our dev call today (Thursday), 5 Sep, at
4 PM BST (3 PM GMT/UTC | 11 AM EST | 8 AM PST).
*Proposed Agenda*:
1) Check in on the action items from the last call
2) Presentation: "Airflow Beach Cleaning" project – Security work (Jarek)
3) Presentation: UI
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,
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
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
+1 binding
On 2024/09/05 11:46:35 Pierre Jeambrun wrote:
> +1 (binding)
>
> On Thu, Sep 5, 2024 at 12:36 PM Utkarsh Sharma
> wrote:
>
> > + 1 Non-binding
> >
> > Thanks,
> > Utkarsh Sharma
> >
> > On Thu, Sep 5, 2024 at 3:06 PM Eugen Kosteev wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Thu
> I had thought that AIP-80 was not going to be in 2.11 anymore, since it
was
My understanding is that it will be "both" - backwards (in Airflow 3) and
forward (in Airflow 2.11) compatible. The problem with AIP-80 being "not
backwards compatible" was really that it will be deprecated only in 2.11
