Re: [Discuss] Improving Airflow UI Testing Coverage

I also think that having a good unit test coverage + e2e tests would really help maintaining quality of releases and prevent regressions early, making all that much more manageable. My two cents regarding the questions above: - Should we prioritize expanding unit test coverage first, or wor

Re: [DISCUSS] dag vs DAG vs Dag

Response thread there. Can’t remember the full outcome from the top of my head but “Dag, dag, dags” seems fine, preferably for doc, new code, user facing, but not worth the trouble going through the whole codebase for refactoring. https://lists.apache.org/thread/8k338stlkkp07ko3no70p2nng757kd1w

Re: [DISCUSS] Updating acceptence criteria for new translations and translation owners

Thanks Shahar for formulating this. A - As long as we agree to it and we have some process to prevent abuse (those mentioned by Daniel or others) I don’t see any harm in accepting any translation. I think our current trusted parties / sponsors system is good for that if we clarify what “trusted”

Re: Add Catalan language to Airflow

an Pierre, that you want to propose and discuss a new rule that > > we should add? What would be that proposed rule in this case (we need to > > have a concrete rule proposal that we can objectively apply to other > > potential languages). Until then I think we should follow the

Re: Add Catalan language to Airflow

Hello guys, I don't want to be rude, or start any political discussion, but I don't see Catalan listed as one of the 24 official EU languages. My question is whether or not we should allow such translations, if we do, we might expect other similar additions which might lead to a lot of translation

Re: [VOTE] Release Apache Airflow from 3.0.4rc2 and TaskSDK from 1.0.4rc1

is the binary Python "sdist" > release. > > >>>> - *apache_airflow-3.0.4-py3-none-any.whl* is the binary Python wheel > > >>>> "binary" release. > > >>>> > > >>>> "apache-airflow-core" package >

Re: [VOTE] Release Airflow 3.0.4 from 3.0.4rc1 & Task SDK 1.0.4 from 1.0.4rc1

+1 binding, tested a bunch of my changes and specifically the connection editing / redacting stuff. On Tue, Aug 5, 2025 at 2:48 PM Jarek Potiuk wrote: > Regenerating the docs with those two commits fixed the issues in staging - > both security model and the diagrams are ok now in staging :) > >

Re: [DISCUSS] Dutch locale is being outdated for 2 consecutive releases

I don’t think this should apply until 3.1.0 is out and internationalisation is released. Basically it can be out of date as long as the translation gap is closed for 3.1.0. IMHO On Mon 4 Aug 2025 at 22:13, Shahar Epstein wrote: > Hey everyone, > > I'd like to point out that the Dutch locale has

Re: [DISCUSS] Merging cherry-picked PRs when green (and actually doing it)

Hello, I also considered that this is the responsibility of the person merging the PR to make sure that it is backported correctly if applicable. (PR opened and merged). I always try to fill in when I see that some PR is missing the backport, but it's harder when this is a PR we didn't follow alon

[HELP NEEDED / Contribution Opportunity] Improve filtering options API and UI

offer your help. Also to mention that this improvement was requested at multiple occasions and I'm sure it will have a very positive impact on the project. Best, Pierre Jeambrun

Re: [VOTE] July 2025 PR of the Month

+1 for #51264 which is a super cool new feature and required some significant effort! On Mon 28 Jul 2025 at 21:08, Jens Scheffler wrote: > A lot of options this one and hard to decide! The top three listed are > the hardest competitors in my view - giving my +1 to #52996 especially > as this is

Re: [VOTE] June 2025 PR of the Month

My vote goes to #51735. We have multiple great PRs this month! Also because I feel it's great to recognize and give merit to the community. (I feel like this award should be reserved to non-committer people). On Fri, Jun 27, 2025 at 9:42 AM Aritra Basu wrote: > Agreed on the two top picks, my v

Re: [ANNOUNCE] New PMC member: Amogh Desai

Congratulations Amogh! Well done! On Thu, Jun 26, 2025 at 3:09 PM Jarek Potiuk wrote: > Congrats Indeed very well deserved! > > On Thu, Jun 26, 2025 at 2:17 PM Aritra Basu > wrote: > > > Congrats Amogh! Very well deserved and love to see it!! > > -- > > Regards, > > Aritra Basu > > > > On T

Re: [LAZY CONSENSUS] Add French Translation (i18n)

ime :) > Nontheless, even if we don't have lazy concencus - I do support at least > announcing the addition of new languages and its owners in the dev. list, > so everyone would be aware of them. > > +1 from me for adding the French language and its suggested owners! > > > S

Re: [LAZY CONSENSUS] Add French Translation (i18n)

pecific language? They already have write access to the code base. > Seems > > odd to vote on granting permission to something they already have. > > > > בתאריך יום ב׳, 16 ביוני 2025, 18:03, מאת Pierre Jeambrun ‏< > > pierrejb...@gmail.com>: > > > > >

Re: [LAZY CONSENSUS] Add French Translation (i18n)

Forgot to add some background for the proposed code owners: - Vincent has been contributing for a while, he has been an Apache Airflow Committer for almost 2 years now. - Pierre is an Apache Airflow PMC member On Mon, Jun 16, 2025 at 4:48 PM Pierre Jeambrun wrote: > Hello, > > This em

[LAZY CONSENSUS] Add French Translation (i18n)

Hello, This email calls for a lazy consensus on: - Accepting French as a supported locale for airflow 3 as part of our i18n policy - Accepting Vincent Beck (https://github.com/vincbeck) as a translation owner for the French translation - Accepting Pierre Jeambrun (https://github.com

Re: [VOTE] Internationalization (i18n) policy

+1 binding, well prepared thanks On Thu 5 Jun 2025 at 15:16, Wei Lee wrote: > +1 binding, with one minor rewording, Taiwanese Mandarin is more accurate. > Thanks for all the hard work :) > > Best, > Wei > > > On Jun 5, 2025, at 6:38 PM, Tamara Fingerlin > wrote: > > > > +1 non-binding > > > > O

Re: [VOTE] May 2025 PR of the Month

+1 for #50626 On Fri, May 30, 2025 at 7:26 PM Shubham Raj wrote: > +1 for #50626 > > > On Fri, 30 May 2025 at 22:02, Shahar Epstein wrote: > > > +1 for #50626 > > > > On Thu, May 29, 2025, 21:00 Jarek Potiuk wrote: > > > > > +1 for #50626 > > > > > > On Thu, May 29, 2025 at 7:54 PM Buğra Öztür

Re: [DISCUSS} Enabled experiment auto-merge feature

Maybe I need to get used to the `escape hatch` (which I don't really like tbh), but I've been having a really hard time not being able to merge things with unrelated CI failure: - Asking people to rebase again numerous time, until CI gets green, for instance https://github.com/apache/airflow/pull/

Re: AW: [ANNOUNCE] Apache Airflow 3.0.0 Released

Amazing! Thanks to everybody that was involved On Wed, Apr 23, 2025 at 10:31 PM Buğra Öztürk wrote: > Amazing milestone! Great work and collaboration! Congrats everyone! > > On Wed, Apr 23, 2025 at 10:57 AM Michał Modras > wrote: > > > This is huge, congratulations to everyone involved! > > > >

Re: [VOTE] Release Airflow 3.0.0 from 3.0.0rc4 & Task SDK 1.0.0 from 1.0.0rc4

+1. Binding. Checked signatures, licences, checksums, reproducibility (and a bunch of sample dags) On Tue, Apr 22, 2025 at 11:34 AM Pavankumar Gopidesu < gopidesupa...@gmail.com> wrote: > +1 non-binding. > > Triggered example dags, looks good. > > Thank you everyone for all the hard work. > > Reg

Re: Au revoir Flask

Nice job! On Tue 8 Apr 2025 at 20:56, Buğra Öztürk wrote: > Amazing news Vincent! Great work! > > On Tue, 8 Apr 2025, 20:52 Ferruzzi, Dennis, > wrote: > > > Great work, all. > > > > > Yay! FABulous milestone! > > > > I believe you mean FAB-u-less? :P > > > > > > - ferruzzi > > > > > > ___

Re: New committer: Rahul Vats

Amazing work Rahul, congratulations. On Mon 31 Mar 2025 at 23:14, Pavankumar Gopidesu wrote: > Woohoo, Congratulations Rahul 🎉🎉 > > Pavan. > > On Mon, Mar 31, 2025 at 9:17 PM Pankaj Koti > wrote: > > > Many congratulations Rahul! Very happy for you and well deserved 🎉🎉 > > > > On Tue, 1 Apr, 20

Re: [VOTE] March 2025 PR of the Month

+1 for https://github.com/apache/airflow/pull/47433 Hard to choose On Tue, Mar 25, 2025 at 2:40 PM Vincent Beck wrote: > My vote goes for https://github.com/apache/airflow/pull/47432. That was a > major security issue with the way the JWT token was exchanged and it got it > fixed after multiple

Re: [DISCUSS] The `uv` as the only supported dev tool

+1 On Sun 23 Mar 2025 at 09:41, Elad Kalif wrote: > +1 > > On Sat, Mar 22, 2025 at 6:11 PM Shahar Epstein wrote: > > > +1 from me - uv is a great tool, improves developer experience, and it is > > well-supported. > > While acknowledging the licensing issues that you mentioned - if > migration >

Re: [DISCUSS] confusing alert re SimpleAuthManager

Is it really wrong to use the SimpleAuthManager in production ? To my knowledge it lacks a lot of features such as user management and the permission model is really simplistic, but maybe some installations don’t need the fancy Auth stuff ? Instead of being a scary warning that could be just an in

Re: New committers: Shubham Raj, Buğra Öztürk, LIU ZHE YOU, Kalyan Reddy !

Thanks for your involvement, congratulations! On Fri 14 Mar 2025 at 18:09, Igor Kholopov wrote: > Congratulations, all! > > On Fri, Mar 14, 2025, 6:07 PM Aritra Basu > wrote: > > > Congrats all! Great job! > > -- > > Regards, > > Aritra Basu > > > > On Fri, 14 Mar 2025, 9:51 pm Josh Fell, > .i

Re: [DISCUSS] Auth backends

I think this is a great way to move forward considering airflow 3 deadline. Also given that this is already implemented and merged in main I’m not sure if an AIP makes sense at this point, I’ll let others weigh in on this. On Tue 4 Mar 2025 at 23:05, Vincent Beck wrote: > Option 1 seems to be th

Re: [VOTE] February 2025 PR of the Month

+1 for https://github.com/apache/airflow/pull/46939 On Wed, Feb 26, 2025 at 6:01 AM Amogh Desai wrote: > +1 for https://github.com/apache/airflow/pull/46942 :D > Thanks & Regards, > Amogh Desai > > > On Wed, Feb 26, 2025 at 8:36 AM Ankit Chaurasia > wrote: > > > +1 for 46942, if it gets merged.

Re: [DISCUSS]: Proposing a "common message queue" abstraction

+1 On Thu, Feb 13, 2025 at 4:36 PM Vincent Beck wrote: > Hi Vikram, > > Thanks for putting it together, I think this is great and will help users > to use event driven scheduling in Airflow 3! > > On 2025/02/13 08:10:05 "Mehta, Shubham" wrote: > > +1 > > > > We should also consider extending thi

Re: 📢 Apache Airflow 3.0.0apha1 is available for testing! 🎉

Amazing news! Well done everybody :) On Sat, Feb 1, 2025 at 2:25 PM Buğra Öztürk wrote: > Awesome news! It feels amazing to be part of this great community! > Kudos all for the immense progress and enormous effort! > > On Sat, Feb 1, 2025 at 12:32 PM Shubham Raj > wrote: > > > Woooww!! It’s rea

Re: [DISCUSS] Drop support for the DAG processor embedded in the scheduler

+1 On Fri, Jan 10, 2025 at 11:01 AM Michał Modras wrote: > +1 - separating these workloads makes sense to me - we remove > unnecessary coupling and make them more single-responsibility, which eases > reasoning about the system and any potential debugging > > > > On Fri, Jan 10, 2025 at 9:15 AM K

Re: [DISCUSS] Consistency of version checks in providers

My two cents: Preventing cross imports and modifying generated files sounds necessary. On the other hand I agree that the CI is complex and having another step of generated code just for simple versions checks might be overkill. On Fri 6 Dec 2024 at 13:02, Jarek Potiuk wrote: > > If the goal i

AIP-84 Public API Migration

Hello all, We just completed the migration of the public API to the new FastAPI server, closing a big one https://github.com/apache/airflow/issues/42370. This new API is feature rich and should feel really familiar; most endpoints, parameters and payloads remain the same - Breaking changes are li

Re: [LAZY CONSENSUS] Use Ruff as the official linter to detect Airflow 3 incompatibilities in user code

That's a nice one, looking forward to it :) On Thu, Nov 21, 2024 at 12:55 PM Tzu-ping Chung wrote: > Hi all, > > I am calling a LAZY CONSENSUS to officially anoint Ruff as the tool to > implement lint rules that detect potential incompatibilities in existing > user code (including DAG files and

Re: [ANNOUNCE] Cherry Picker Automation Now in GitHub Actions!

Great news, can't wait to try this one out, thanks! On Mon, Nov 18, 2024 at 1:51 PM Pavankumar Gopidesu wrote: > Yes Great question :), When the backport succeeds or failed, a > comment will be added to original PR > > eg: https://github.com/apache/airflow/pull/44081#issuecomment-2480855391 > >

Re: [ANNOUNCE] New PMC member: Vikram Koka

Congratulations Vikram! On Sat 19 Oct 2024 at 21:19, Jens Scheffler wrote: > Welcome Vikram! Well deserved! > > On 19.10.24 21:02, Kaxil Naik wrote: > > Dear Airflow Community, > > > > The Project Management Committee (PMC) for Apache Airflow has invited > *Vikram > > Koka *to become a PMC membe

Re: UI and API Contributions for Airflow 3.0

to tackle by the newly formed CI/CD team. > > > > J. > > > > On Thu, Sep 5, 2024 at 2:13 PM Pierre Jeambrun > > wrote: > > > >> Thanks Brent. > >> > >> Yes I like the idea of labels, I believe this will help reviewers know > >&g

Re: UI and API Contributions for Airflow 3.0

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,

Re: [VOTE] August 2024 PR of the Month

Just to mention that there is no binding / non-binding vote for this thread. Everybody has a vote and counts for 1 for the final result. All members of the community are welcomed to champion their favorite PR :) On Fri, Aug 30, 2024 at 11:28 AM Ankit Chaurasia wrote: > +1 for 41390 (Non-bindi

Re: [VOTE] August 2024 PR of the Month

+1 for PR #41390 On Tue, Aug 27, 2024 at 10:59 PM Scheffler Jens (XC-AS/EAE-ADA-T) wrote: > +1 binding for 41390 - subdags gone is a great step forward! > > Sent from Outlook for iOS > > From: Briana Okyere > Sent: Tuesday, August 27, 2024

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham wrote: > +1 >

Re: [DISCUSS] New provider Common.time

I also like core Le ven. 16 août 2024 à 11:48, rom sharon a écrit : > +1 for “core” >

Re: [ANNOUNCE] New PMC member: Jens Schaffler

Congratulations Jens! Le lun. 12 août 2024 à 20:53, Ferruzzi, Dennis a écrit : > Congratulations Jens, well deserved. > > > - ferruzzi > > > > From: Mehta, Shubham > Sent: Wednesday, August 7, 2024 1:39 PM > To: dev@airflow.apache.org > Subject: RE: [EXT] [ANNO

Re: [ANNOUNCE] New PMC member: Jens Schaffler

Congratulations Jens! On Tue 6 Aug 2024 at 10:08, Buğra Öztürk wrote: > Congratulations Jens 🎊🎉 > > On Tue, 6 Aug 2024, 10:04 Pankaj Koti, > wrote: > > > Many congratulations, Jens!! 🎉🎉🎉 > > > > Best regards, > > > > *Pankaj Koti* > > Senior Software Engineer (Airflow OSS Engineering team) > >

Re: [VOTE] AIP-79 & AIP-84 Remove Flask AppBuilder as a Core Dependency & UI REST API

+1 (binding On Mon 5 Aug 2024 at 08:17, Ephraim Anierobi wrote: > +1 (binding) > > On Mon, 5 Aug 2024 at 03:58, Vishnu Chilukoori > wrote: > > > +1 (non-binding) for both > > > > On Sun, Aug 4, 2024 at 7:07 PM Wei Lee wrote: > > > > > +1 (binding) for both APIs > > > > > > Best, > > > Wei > >

Re: AWS Open Source Credits Program

Great news! On Sat 27 Jul 2024 at 01:15, Sadha Chilukoori wrote: > That's wonderful news. > > On Fri, Jul 26, 2024 at 12:34 PM Oliveira, Niko > > wrote: > > > Hello folks, > > > > This is a short note to announce that the AWS Open Source Credits Program > > has approved us for another round of

Re: [ANNOUNCE] New committers: Rom Sharon & Shahar Epstein

Congrats! On Tue 16 Jul 2024 at 09:04, Scheffler Jens (XC-AS/EAE-ADA-T) wrote: > Welcome Rom and Shahar! > > Mit freundlichen Grüßen / Best regards > > Jens Scheffler > > Alliance: Enabler - Tech Lead (XC-AS/EAE-ADA-T) > Robert Bosch GmbH | Hessbruehlstraße 21 | 70565 Stuttgart-Vaihingen | > GER

Re: [ANNOUNCE] New committer: Ryan Hatter

Well done Ryan :) Le ven. 28 juin 2024 à 19:42, Ferruzzi, Dennis a écrit : > Hey, congrats! > > > - ferruzzi > > > > From: Pankaj Koti > Sent: Friday, June 28, 2024 10:21 AM > To: dev@airflow.apache.org > Subject: RE: [EXT] [ANNOUNCE] New committer: Ryan Hatter

Re: [PROPOSAL] Automated managemenet of lower-bounds of airflow dependencies

Great work! That sounds like a really nice improvement :) Le sam. 1 juin 2024 à 10:48, Jarek Potiuk a écrit : > Hello everyone, > > TL;DR; I have finally got to something we planned when we switched to UV, I > have a green PR where we introduced automated management of "lower-bounds" > dependenc

Re: [DISCUSS] indexes for API calls

Indeed Jarek I feel like this is another point in favor of stick to "Postgres" As mentioned, maybe we were a little reckless when adding all these kinds of filters. If they are not often used and we rarely / never see performance github issues on those, marking them as 'non optimised but here for

Re: [DISCUSS] Restore the SQL server backend

I share Jed feeling. The effort required to maintain those compare to the value it actually brings combined with the usage from the survey, it doesn’t seem worth it to me. On Thu 30 May 2024 at 19:16, Jed Cunningham wrote: > Just for context, here were (roughly) the results from the 2023 Airflow

Re: [DISCUSS] indexes for API calls

Thank you for starting this discussion. At first I would say that databases should be indexed to achieve good performances against standard queries / use cases. The Rest API does not do any crazy things/querying (as I recall). Listing, filtering, ordering and searching against our main tables sho

Re: [VOTE] May 2024 PR of the Month

Well, the task try_number was an issue for as long as I can remember and we had a few tries attempting to fix it in the past, it was a pain to work with. I am really glad to see it in a more stable state, good job! +1 for #39336 On Wed 29 May 2024 at 10:50, Bas Harenslak wrote: > My vote goes

Re: [HUGE DISCUSSION] Airflow3 and tactical (Airflow 2) vs strategic (Airflow 3) approach

Thank you for the work and proposal made around airflow 3. I also strongly believe that those important changes need to happen for airflow to stay relevant and it would be the right moment to start discussing and planning for airflow 3. As mentioned some features are hard to develop within airflow

Re: [VOTE] AIP-67 Multi-team deployment of Airflow components

+1 (binding) Le jeu. 18 avr. 2024 à 18:52, Ferruzzi, Dennis a écrit : > This is exciting. +1 binding. > > > - ferruzzi > > > > From: Oliveira, Niko > Sent: Thursday, April 18, 2024 9:16 AM > To: dev@airflow.apache.org > Subject: RE: [EXTERNAL] [COURRIEL EXTERN

Re: [ANNOUNCE] New committer: Wei Lee

Congratulations! Le lun. 8 avr. 2024 à 16:49, Wei Lee a écrit : > Thanks for all your support 🙏 Can’t be more excited 🤩 > > Best, > Wei > > > On Apr 8, 2024, at 9:15 PM, Vincent Beck wrote: > > > > Congrats Wei! Well deserved! > > > > On 2024/04/08 13:03:50 Hemkumar Chheda wrote: > >> Congratul

Re: [VOTE] AIP-64: Keep TaskInstance try history

+1 (binding) On Mon 25 Mar 2024 at 19:32, Igor Kholopov wrote: > +1 (non-binding) > > On Mon, Mar 25, 2024 at 7:28 PM Tzu-ping Chung > wrote: > > > +1 binding. > > > > This is something we should just do even outside of the DAG versioning > > context (which we also should do, to be clear). > >

Re: [DISCUSS] Deprecate cli options in Airflow Configurations and airflow.api.client

+1, stable API should be favoured On Tue 20 Feb 2024 at 16:10, Jarek Potiuk wrote: > Oh God . What an archeology. Yeah I think we had a limite when we discussed > it then (looking at the discussion) we did not have a solid replacement yet > (and the discussion was about deprecating it in 1.10).

Re: [DISCUSS] Considering trying out uv for our CI workflows

I can definitely see benefits and I would be in favour of using it in our CI jobs, allowing for faster and more robust pipeline (alternative resolution etc…) As Jarek mentioned, it is not aimed to be a user facing change, just internal to make things easier. We have cases (Sbom generation for prov

Re: Idea for Discussion: custom TI dependencies

ore questions/comments! > > > > > > XD > > > > > > > On Feb 2, 2024, at 13:29, Constance Martineau .INVALID> > > wrote: > > > > > > Naive question: Instead of running the code on the scheduler - could > the > > > conditio

Re: Idea for Discussion: custom TI dependencies

But maybe it’s time to reconsider that :), curious to see what others think. On Fri 2 Feb 2024 at 20:30, Pierre Jeambrun wrote: > I like the idea and I understand that it might help in some use cases. > > The first concern that I have is that it would allow user code to run in > t

Re: Idea for Discussion: custom TI dependencies

I like the idea and I understand that it might help in some use cases. The first concern that I have is that it would allow user code to run in the scheduler, if I understand correctly. This would have big implications in terms of security and how our security model works. (For instance the schedu

Re: [ANNOUNCE] New PMC member: Andrey Anshin (taragolis)

Congratulations Andrey! On Mon 15 Jan 2024 at 19:35, Jarek Potiuk wrote: > I have the pleasure to announce that The Project Management Committee > (PMC) for Apache Airflow has invited Andrey Anshin (taragolis) to become > Apache > Airflow PMC Member and we are pleased to announce that he has kin

Re: [PROPOSAL] Standardize Airflow Packaging and build process (modern appropriate PEP-compliant tooling)

I personally think that this is a great idea. I have been following the hatch project for a while and I am convinced it has a lot to offer for airflow. The two big pros for me are its ease of use (backend and front end) as well as the security covered aspects (reproducible builds to name one). I w

Re: [VOTE] December PR of the Month

+1 for #35926, great work! Really glad to see this happening and giving me hope for a much cleaner/flexible webserver code. On Wed 3 Jan 2024 at 14:53, wrote: > +1 for 35719 > > > On Jan 2, 2024, at 11:14 PM, Amogh Desai > wrote: > > > > My vote goes to #35719. Having a nice UI fix come in, th

Re: [DISCUSSION] Enabling `pre-commit.ci` application for Airflow

I like the idea, but in practice auto fixable static checks are very obvious to fix and doesn’t require much work. On the other hand most of static failure are ‘real issues’ and not auto fixable, for instance mypy, spelling, sphinx, db session usage etc…. (And ruff fix is a little aggressive IMO r

Re: [DISCUSS] "Require conversation resolution" in our PRs before merge?

This is something I already try to apply on my own PRs, never merge before explicitly solving all conversations. Also for a reviewer, I feel like this gives more confidence to the fact that the PR is ready, and indeed we are less subject to missing a discussion or something going on making it 'not

Re: Making Listeners API non-experimental

+1 On Fri 15 Dec 2023 at 17:46, Aritra Basu wrote: > +1 > > -- > Regards, > Aritra Basu > > On Fri, Dec 15, 2023, 8:47 PM Vincent Beck wrote: > > > +1 > > > > On 2023/12/15 12:51:26 Jarek Potiuk wrote: > > > +1. ESPECIALLY if there will be issues found that we will fix in 2.8.x > :D > > > > > >

Re: [ANNOUNCE] New committer: Utkarsh Sharma

Congratulations! Le lun. 4 déc. 2023 à 20:18, Andrey Anshin a écrit : > Congrats! 🔥💯 > > > > > On Mon, 4 Dec 2023 at 22:45, Amogh Desai wrote: > > > This is fantastic! Congratulations Utkarsh. > > > > Well deserved! > > > > Thanks & Best Regards, > > Amogh Desai > > > > > > On Mon, 4 Dec 2023 a

Re: [DISCUSS] Suspend/Remove Apache Scoop provider

+1 Le jeu. 23 nov. 2023 à 17:52, Hussein Awala a écrit : > +1 > > On Thu, Nov 23, 2023 at 11:52 AM Andrey Anshin > wrote: > > > Greetings everyone! > > > > Since we began to actively use the mechanism to suspend/remove providers > I > > want to start the discussion about suspend and potential r

Re: [VOTE] Release Airflow Python Client 2.7.3 from 2.7.3rc1

+1 (binding), checksums, signatures and licenses look good. (also ran a few sample requests against breeze instance) Le lun. 13 nov. 2023 à 23:20, Hussein Awala a écrit : > +1 (binding) I tested it by triggering some dag runs and running other API > requests, and all looks good. > > On Tue, Nov

Re: [LAZY CONSENSUS] Decouple Core and API Clients versioning

Lazy consensus has been reached. I will follow through with updating the relevant documentation and we can start working on the next major version for clients. Best regards, Le dim. 5 nov. 2023 à 23:05, Pierre Jeambrun a écrit : > Hey fellow Airflowers, > > As discussed i

Re: [ANNOUNCE] New committer: Jens Scheffler

Congrats Jens! Le mer. 8 nov. 2023 à 09:40, Pankaj Koti a écrit : > Many congratulations, Jens!! 🎉 🏆 > > > Best regards, > > *Pankaj Koti* > Senior Software Engineer (Airflow OSS Engineering team) > Location: Pune, Maharashtra, India > Timezone: Indian Standard Time (IST) > Phone: +91 9730079985

[LAZY CONSENSUS] Decouple Core and API Clients versioning

objection, lazy consensus will be reached on Sunday, 12th November. Pierre Jeambrun

Re: [DISCUSS] API Clients Major version

;t we release a new package 'python-client-nextgen' & with new > > build > > > process/generator and release process following the same versioning as > > > previously.. > > > > > > > > > The old python client will c

Re: [VOTE] Release Airflow 2.7.3 from 2.7.3rc1

+1 (binding). Checksums, signatures, licences and sources look good. Ran a few simple DAGs as well. Le jeu. 2 nov. 2023 à 13:42, Ephraim Anierobi a écrit : > Hey fellow Airflowers, > > I have cut Airflow 2.7.3rc1. This email is calling a vote on the release, > which will last at least 72 hours,

[DISCUSS] API Clients Major version

Hello, This thread was originated from: https://github.com/apache/airflow/pull/34805 that tries to upgrade the generator version to 7.0.1. *Motivations/Context:* New versions of the openapi generator hold breaking changes in regards to the clients code generated. For this reason, up to now we cho

Re: [VOTE] October 2023 PR of the Month

+1 to 34729 Le mer. 1 nov. 2023 à 06:47, Avi a écrit : > +1 for 34729 > > Reagrds, > Avi > > > On Wednesday, Nov 01, 2023 at 05:44, utkarsh sharma < > utkarshar...@gmail.com (mailto:utkarshar...@gmail.com)> wrote: > > +1 for 34729 :) great work on that. > > > > Thanks, > > Utkarsh Sharma > > > >

Re: [PROPOSAL] Explain what milestones mean in our PRs/Issues - what users can expect

There is already a whole section about Semver in the README, maybe we can just link to it ? Le dim. 29 oct. 2023 à 18:36, Pierre Jeambrun a écrit : > I think this is a good idea. Speaking for myself, it wasn't clear to me > until I got involved in the release process. > > In

Re: [PROPOSAL] Explain what milestones mean in our PRs/Issues - what users can expect

I think this is a good idea. Speaking for myself, it wasn't clear to me until I got involved in the release process. In that PR, I think mentioning semver and pointing to the spec could be helpful. Le sam. 28 oct. 2023 à 22:14, Jarek Potiuk a écrit : > Hey everyone, > > We had some discussions

Re: [DISCUSS] Removing Qubole provider (and adding removal process)

+1 Le ven. 27 oct. 2023 à 19:16, Aritra Basu a écrit : > Sounds like a good time to set the process up. +1 from me as well. > > -- > Regards, > Aritra Basu > > On Fri, Oct 27, 2023, 6:42 PM Vincent Beck wrote: > > > I like that. I also think it is important to have a process to remove > > provi

Re: [VOTE] Add Multiple PR's of the Month to the Airflow Newsletter

Hello all, I like the idea of highlighting more than just 1 PR in the "PR of the month section", especially when we have a hard time deciding between a few good candidates. IMHO the script does not always select good candidates or sometimes miss some good candidates, (because of the heuristic we

Re: [VOTE] Add providers for Pinecone, OpenAI & Cohere to enable first-class LLMOps

+1 (binding) Le mer. 25 oct. 2023 à 13:29, Pankaj Singh a écrit : > +1 (binding) > > On Wed, Oct 25, 2023 at 4:52 PM Amogh Desai > wrote: > > > +1 (binding) > > > > On Wed, Oct 25, 2023 at 4:41 PM Phani Kumar > > wrote: > > > > > +1 binding > > > > > > On Wed, 25 Oct 2023, 16:39 utkarsh sharma

Re: Limiting (or errorring out) Airflow for Python 3.12 until our dependencies/we catch up

I think that limiting to <3.12 makes sense. 2.7.2 is already out so I'm not sure we can do anything for users trying to install 2.7.2 on python 3.12. I believe there is no such thing as a python minor that is out of the box working well for airflow. It seems that we always need extra efforts to br

Re: [DISCUSSION] Add 5 new Providers to enable first-class LLMOps

+1 from me as well. Indeed LLMs for Apache Airflow is a no brainer, this will open a lot of opportunities for our users. Having Astronomer supporting this initiative is great. I like the idea of system tests dashboard, especially for those that are not open source/easily testable without a paid a

Re: The "no_status" state

Seems like a good idea. Some kind of "task diagnosis", in case the state is not settled to give more context to users. Happy to help on that one as well. I also think that a small AIP is required, the scope of change could be substantial. Best regards, Pierre Le jeu. 19 oct. 2023 à 17:05, Brent

Re: Airflow Docs Development Issues

+1 from moving archived docs outside of airflow-site. Even if that might mean a little more maintenance in case we need to propagate changes to all historical versions, we would have to handle 2 repositories, but that seems like a minor downside compared to the quality of life improvement that it

Re: [VOTE] Release Airflow Python Client 2.7.2 from 2.7.2rc1

+1 (binding). Licences, checksums and signatures look good. Also ran a few api requests against my local install, working as expected. Le ven. 13 oct. 2023 à 09:12, Ephraim Anierobi a écrit : > Hey fellow Airflowers, > > I have cut the release candidate for the Airflow Python Client 2.7.2rc1. >

Re: [VOTE] September 2023 PR of the Month

+1 for 28900 On Fri 29 Sep 2023 at 23:14, Mehta, Shubham wrote: > + 1 to #28900. That required a lot of perseverance > > Shubham > > On 2023-09-29, 2:09 PM, "Briana Okyere" LID> wrote: > > > CAUTION: This email originated from outside of the organi

Re: [ANNOUNCE] Pankaj Koti and Amogh Desai as committers

Congratulations to both of you, well deserved :) Le mer. 20 sept. 2023 à 00:50, Akash Sharma <2akash111...@gmail.com> a écrit : > Congrats Pankaj and Amogh. > > Best regards, > Akash > > On Tue, 19 Sep 2023, 23:33 Sameer Ahmad Siddiqui, < > sameerahmad@gmail.com> > wrote: > > > Congrats Panka

Re: [DISCUSS] Preventing users from misusing _PIP_ADDITIONAL_REQUIREMENTS ?

Maybe we can introduce a global “DEBUG” config option/env variable. This could control some more verbose logging but most importantly only when this is turned on, we could use the sequential executor, debug executor, _PIP_ADDITIONAL_REQUIREMENTS and any other “debug/development” purpose options. L

Re: [DISCUSS] move from semver to a more "rolling" release cycle for core

Same, I was very tempted by this at first but Jarek and Niko changed my mind. I think sticking to semver will be more beneficial in the long run. On Wed 30 Aug 2023 at 04:09, Mehta, Shubham wrote: > I couldn’t agree more with Jarek and Niko's perspective on the importance > of maintaining SemVer

Re: [VOTE] August 2023 PR of the Month

Tough call, +1 for @eumiro work. On Wed 30 Aug 2023 at 04:06, Wei Lee wrote: > +1 to #30259 > > Best, > Wei > > > On Aug 30, 2023, at 12:59 AM, Frank Cash wrote: > > > > +1 to #30259. > > > > > > On Tue, Aug 29, 2023 at 1:27 AM Amogh Desai > > wrote: > > > >> Wasn't aware of things done by @eu

Re: [VOTE] Drop MsSQL as supported backend

+1 (binding) Le lun. 28 août 2023 à 17:11, Vincent Beck a écrit : > +1 binding > > On 2023/08/28 07:55:17 Jarek Potiuk wrote: > > (just add that my voice is binding :) ) > > > > On Mon, Aug 28, 2023 at 9:35 AM Amogh Desai > > wrote: > > > > > +1 non binding > > > Based on previous discussions.

Re: [VOTE] Release Airflow Python Client 2.7.0 from 2.7.0rc1

+1 binding - signatures, checksums, licences looks good. 2.7.0 client was expected to solve a few reported issues, (nullable refs). Tested those and it looks fine as well. Le mer. 23 août 2023 à 18:02, Jarek Potiuk a écrit : > +1 binding - checked signatures, checksums, run a few tests with air

Re: [DISCUSS] Drop MsSQL as supported backend

I am also in favor of dropping MSSQL. We have seen a lot of trouble with this particular backend, and with the data points you mentioned it definitely seems that it's not worth all the efforts to maintain it. Le ven. 18 août 2023 à 16:28, Wei Lee a écrit : > +1 (non binding) > > I agree with thi

Re: [VOTE] Release Airflow 2.7.0 from 2.7.0rc2

+1 (binding) Checksum, signatures, licences and release artifacts look good to me. Ran a few tests, working as expected. Le mer. 16 août 2023 à 21:48, Pankaj Singh a écrit : > +1 (non-binding) > > Ran astro-sdk tests and tested my changes. > > On Wed, Aug 16, 2023 at 11:23 PM Ferruzzi, Dennis >

Re: [VOTE] Restore dag_run.conf UI triggering option for 2.7.0

+1 (binding) Le sam. 12 août 2023 à 19:50, Jarek Potiuk a écrit : > Tuesday 10am 15th (!) of August, 2023 of course, not 26th. That would be > quite a delay. > > On Sat, Aug 12, 2023 at 7:48 PM Hussein Awala wrote: > > > Thank you Jarek for raising this vote. > > > > +1 (binding) > > > > On Sat

  1   2   >