Vibe coding to the max!

I would love to try it out once too :D

Thanks & Regards,
Amogh Desai


On Sat, Jun 28, 2025 at 5:44 PM Jarek Potiuk <ja...@potiuk.com> wrote:

> This is super nice - and the super-detailed AI-centered instructions are
> extremely helpful - if you have access to some AI agents, it can
> definitely speed up the process - leaving you in full control and making
> sure that you drive the PR to greenes and review if whatever AI generated
> is cool.
>
> On Sat, Jun 28, 2025 at 1:53 PM Blain David <david.bl...@infrabel.be>
> wrote:
>
> > I'm willing to help to migrate the Microsoft Azure one and maybe common
> > SQL as I already have some experience there and those are well known
> > providers to me.
> >
> > -----Original Message-----
> > From: Kaxil Naik <kaxiln...@gmail.com>
> > Sent: Saturday, June 28, 2025 2:23 AM
> > To: dev@airflow.apache.org
> > Subject: [HELP NEEDED / Contribution Opportunity] Update `BaseOperator`
> > imports for Airflow 3.0 compatibility
> >
> > EXTERNAL MAIL: Indien je de afzender van deze e-mail niet kent en deze
> > niet vertrouwt, klik niet op een link of open geen bijlages. Bij twijfel,
> > stuur deze e-mail als bijlage naar ab...@infrabel.be<mailto:
> > ab...@infrabel.be>.
> >
> > Hello folks,
> >
> > Happy weekend.
> >
> > We need community help to migrate all provider packages to use the new
> > Task SDK BaseOperator import for Airflow 3.0 compatibility while
> > maintaining backward compatibility with Airflow 2.x.
> >
> > Details in https://github.com/apache/airflow/issues/52378
> >
> > Standard & Google providers have been migrated and merged which can be
> > used as a good reference:
> >
> > - https://github.com/apache/airflow/pull/52366
> > - https://github.com/apache/airflow/pull/52292
> >
> > Thanks, looking forward for contributions.
> >
> > Regards,
> > Kaxil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > For additional commands, e-mail: dev-h...@airflow.apache.org
> >
> >
>

Reply via email to