Re: [VOTE] January 2024 PR of the Month

#45563 +1, this is awesome! and thanks all for mentioning #45678 Best, Wei > On Jan 31, 2025, at 1:42 PM, Shahar Epstein wrote: > > Hey everyone and apologies for the delay - I'd like to appreciate > everyone's support for the Sphinx PR, > and thank Jarek and Jens for helping out :) > I'll cast

Re: [VOTE] January 2024 PR of the Month

Hey everyone and apologies for the delay - I'd like to appreciate everyone's support for the Sphinx PR, and thank Jarek and Jens for helping out :) I'll cast my vote for #45627 - crucial step for supporting mapped tasks, so kudos for Ash, Kaxil and Jens for promoting that! Shahar On Tue, Jan 28,

Re: [VOTE] January 2024 PR of the Month

+1 for #45563 Tough choice indeed, but I’d also like to cast my vote for *#45563 (Sphinx Upgrade)*. Huge thanks to Shahar for driving this forward and to Jens and Jarek for the support. As Jarek mentioned, groundwork like this often flies under the radar but is critical to long-term project sustai

Re: [VOTE] January 2024 PR of the Month

+1 for #45563 THANKS to Shahar for taking the lead! Agree wit Jarek. Hope somebody has capacity and energy to fix other Docs problems upcoming. But in general a tough choice this month with sooo many great contributions. Also want to explicity thank Wei for the newsfragment cleanup and *vatsrahu

Re: [VOTE] January 2024 PR of the Month

+1 for #45563 (Sphinx). A very good first step forward! On 2025/01/28 08:34:31 Jarek Potiuk wrote: > Yeah, I am also for Sphinx #45563. > > I think we have plenty of "new feature" PRs that a lot of busy folks are > working on so this is really a tough one, but I think those PR will be > praised a

Re: [VOTE] January 2024 PR of the Month

Yeah, I am also for Sphinx #45563. I think we have plenty of "new feature" PRs that a lot of busy folks are working on so this is really a tough one, but I think those PR will be praised and touted (and people working on them collectively and individually) when we go to release announcements, and

Re: [VOTE] January 2024 PR of the Month

Anyways, tough set of choices definitely!! My vote goes to #45563. Good job Shahar and everyone who assisted him. (Jens and Jarek if I am not mistaken) Thanks & Regards, Amogh Desai On Tue, Jan 28, 2025 at 12:59 PM Amogh Desai wrote: > I wonder why the format of PR candidates look like this:

Re: [VOTE] January 2024 PR of the Month

I wonder why the format of PR candidates look like this: *PR #45627: Start porting mapped task to SDK >>* The f

Re: [VOTE] January 2024 PR of the Month

Tough month! My vote goes to the sphinx upgrade, #45563.

Re: [VOTE] January 2024 PR of the Month

We had 4 PRs that were tagged PROTM , only 1 made it onto this list though. The 3 that didn't make it are: PR #45563: Upgrade sphinx and related dependencies https://github.com/apache/airflow/pull

[VOTE] January 2024 PR of the Month

Hey All, Goodness, this month went by swiftly... It’s once again time to vote for the PR of the Month! With the help of the `get_important_pr_candidates` script in dev/stats, we've identified the following candidates: PR #45627: Start porting mapped task to SDK < https://github.com/apache/airfl

Re: [VOTE] January 2024 PR of the Month

+1 for #34225. A lot of work went into that, and it really improves how the service works. From: Andrey Anshin Sent: Wednesday, February 28, 2024 8:58:37 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] January 2024 PR of the Month

Re: [VOTE] January 2024 PR of the Month

ruary 27, 2024 6:18:41 AM > > To: dev@airflow.apache.org > > Subject: Re: [VOTE] January 2024 PR of the Month > > > > I want to nominate #36797.[1] > > > > This one has been a pretty popular request as well.[2] arguably dating > > even further bac

Re: [VOTE] January 2024 PR of the Month

look for iOS<https://aka.ms/o0ukef> > > From: Tzu-ping Chung > Sent: Tuesday, February 27, 2024 6:18:41 AM > To: dev@airflow.apache.org > Subject: Re: [VOTE] January 2024 PR of the Month > > I want to nominate #36797.[1] > > Th

Re: [VOTE] January 2024 PR of the Month

he.org Subject: Re: [VOTE] January 2024 PR of the Month I want to nominate #36797.[1] This one has been a pretty popular request as well.[2] arguably dating even further back since dynamic task mapping was first launched. Nobody bothered to put in the effort until Ryan stepped up. January was a

Re: [VOTE] January 2024 PR of the Month

+1 on #36797 On Tue, Feb 27, 2024 at 2:39 AM Jarek Potiuk wrote: > Thanks TP, for bringing it :) > > If I can split my vote between #37101 and #36797 - > that would be it > > On Tue, Feb 27, 2024 at 6:19 AM Tzu-ping Chung > wrote: > > > I want to n

Re: [VOTE] January 2024 PR of the Month

Thanks TP, for bringing it :) If I can split my vote between #37101 and #36797 - > that would be it On Tue, Feb 27, 2024 at 6:19 AM Tzu-ping Chung wrote: > I want to nominate #36797.[1] > > This one has been a pretty popular request as well.[2] arguably dating > even further back since dynamic

Re: [VOTE] January 2024 PR of the Month

I want to nominate #36797.[1] This one has been a pretty popular request as well.[2] arguably dating even further back since dynamic task mapping was first launched. Nobody bothered to put in the effort until Ryan stepped up. January was a month with multiple such stories. Two are already nomin

Re: [VOTE] January 2024 PR of the Month

I'm down for #37101 too, but we might consider including #37016 as well. The former is just a simpler interface for the latter.

Re: [VOTE] January 2024 PR of the Month

+1 for #37101 too! This will make datasets more usable and it is a step in the right direction! Thanks & Regards, Amogh Desai On Tue, Feb 27, 2024 at 7:00 AM Wei Lee wrote: > +1 for #37101 > > Best, > Wei > > Kenten Danas 於 2024年2月27日 週二 上午5:28寫道： > > > +1 for #37101 - sooo many requests for

Re: [VOTE] January 2024 PR of the Month

+1 for #37101 Best, Wei Kenten Danas 於 2024年2月27日 週二 上午5:28寫道： > +1 for #37101 - sooo many requests for this, the community will be very > happy to have this implemented! > > On Mon, Feb 26, 2024 at 11:52 AM Jarek Potiuk wrote: > > > +1 on #37101 -> I think all the changes that make the datas

Re: [VOTE] January 2024 PR of the Month

+1 for #37101 - sooo many requests for this, the community will be very happy to have this implemented! On Mon, Feb 26, 2024 at 11:52 AM Jarek Potiuk wrote: > +1 on #37101 -> I think all the changes that make the dataset feature more > powerful (and especially one that our users definitely asked

Re: [VOTE] January 2024 PR of the Month

+1 on #37101 -> I think all the changes that make the dataset feature more powerful (and especially one that our users definitely asked for) is a really cool way to make our users look at Airflow through the lens of "modern and slick". This one is definitely taking us closer to this goal. On Mon,

[VOTE] January 2024 PR of the Month

Hey All, It’s once again time to vote for the PR of the Month. With the help of the `get_important_pr_candidates` script in dev/stats, we've identified the following candidates: PR #37058: AIP-58: Add object storage backend for xcom < https://github.com/apache/airflow/pull/37058> PR #37101: I

Re: [RESULT][VOTE] January 2024 PR of the Month

Ohh haha. Mail was trickling on slowly. Well deserved Jarek. Sent from my iPhone > On 30 Jan 2024, at 20:07, Briana Okyere > wrote: > > Hey All, > > Congratulations to Jarek on winning PR of the Month for January 2044 with PR > #36537: Standardize airflow build process and switch to Hatchlin

Re: [VOTE] January 2024 PR of the Month

> Sent from Outlook for iOS<https://aka.ms/o0ukef> <https://aka.ms/o0ukef>;> > > From: Hussein Awala mailto:huss...@awala.fr>> > Sent: Tuesday, January 23, 2024 9:12 PM > To: dev@airflow.apache.org <mailto:dev@airflow.a

[RESULT][VOTE] January 2024 PR of the Month

Hey All, Congratulations to Jarek on winning PR of the Month for January 2044 with PR #36537: Standardize airflow build process and switch to Hatchling build backend. Well deserved Jarek! PR #36537 will be featured in the January 2024 Newsletter, and

Re: [VOTE] January 2024 PR of the Month

__ From: Hussein Awala mailto:huss...@awala.fr>> Sent: Tuesday, January 23, 2024 9:12 PM To: dev@airflow.apache.org <mailto:dev@airflow.apache.org> mailto:dev@airflow.apache.org>> Subject: Re: [VOTE] January 2024 PR of the Month +1 for #36537 On Tue, Jan 23

Re: [VOTE] January 2024 PR of the Month

Sent: Tuesday, January 23, 2024 9:12 PM To: dev@airflow.apache.org Subject: Re: [VOTE] January 2024 PR of the Month +1 for #36537 On Tue, Jan 23, 2024 at 3:40 PM Andrey Anshin wrote: > My vote goes to #36537. > But I think we should mention PR #22253 as a PR which finally merged - >

Re: [VOTE] January 2024 PR of the Month

+1 for #36537 On Tue, Jan 23, 2024 at 3:40 PM Andrey Anshin wrote: > My vote goes to #36537. > But I think we should mention PR #22253 as a PR which finally merged - > "keep calm and add changes" > > > On Tue, 23 Jan 2024 at 17:36, Wei Lee wrote: > > > My vote is for #36537. Love this packaging

Re: [VOTE] January 2024 PR of the Month

My vote goes to #36537. But I think we should mention PR #22253 as a PR which finally merged - "keep calm and add changes" On Tue, 23 Jan 2024 at 17:36, Wei Lee wrote: > My vote is for #36537. Love this packaging improvement! > > Best, > Wei > > > On Jan 23, 2024, at 10:30 PM, Ryan Hatter > >

Re: [VOTE] January 2024 PR of the Month

My vote is for #36537. Love this packaging improvement! Best, Wei > On Jan 23, 2024, at 10:30 PM, Ryan Hatter > wrote: > > Gotta agree with Constance and go with 22253 -- how cool that the author > stuck with it all this time! > > On Tue, Jan 23, 2024 at 12:25 AM Aritra Basu > wrote: > >> M

Re: [VOTE] January 2024 PR of the Month

Gotta agree with Constance and go with 22253 -- how cool that the author stuck with it all this time! On Tue, Jan 23, 2024 at 12:25 AM Aritra Basu wrote: > My vote is for #36537 it's been a huge effort and it makes huge > improvements in our packaging. Great to see it make it into airflow. > > -

Re: [VOTE] January 2024 PR of the Month

My vote is for #36537 it's been a huge effort and it makes huge improvements in our packaging. Great to see it make it into airflow. -- Regards, Aritra Basu On Tue, Jan 23, 2024, 10:13 AM Amogh Desai wrote: > Is there a possibility to vote for more than one? I guess not :/ > > My vote goes to #

Re: [VOTE] January 2024 PR of the Month

Is there a possibility to vote for more than one? I guess not :/ My vote goes to #36537 for the enhancements that have come in with it. I have followed the discussions at a higher level and it surely wasn't easy :) (If I could vote again, it would surely be #36537 for the endless perseverance and

Re: [VOTE] January 2024 PR of the Month

Heck, why not. I will shamelessly vote on my #36537. While it took just a few weeks to merge, It leapfrogged our legacy packaging setup to more-or-less bleeding edge from what was there since the beginning of Airflow (almost 10 years) and was already "old-ish" when I joined the project more than 4

Re: [VOTE] January 2024 PR of the Month

+1 #22253 The PR was opened in March 2022, and was finally merged last week! I admire the author's persistence in getting this merged in, and think the simplifications to the interface make the Operator more user-friendly for our Data Science users. On Mon, Jan 22, 2024 at 1:29 PM Briana Okyere

[VOTE] January 2024 PR of the Month

Hey All, It’s once again time to vote for the PR of the Month. With the help of the `get_important_pr_candidates` script in dev/stats, we've identified the following candidates: PR #36513: Include plugins in the architecture diagrams. PR #32867: Sa