You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Briana Okyere <br...@astronomer.io.INVALID> on 2025/01/27 22:43:21 UTC
[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/airflow/pull/45627
<https://github.com/apache/airflow/pull/44332>>
PR #45924: AIP-72: Port Registering of Asset Changes to Task SDK on task
completion <https://github.com/apache/airflow/pull/45924
<https://github.com/apache/airflow/pull/44972>>
PR #44533: Update conf column in dag_run table type from bytes to JSON <
https://github.com/apache/airflow/pull/44533
<https://github.com/apache/airflow/pull/44712>>
PR #45270: Migrate trigger form params to new UI <
https://github.com/apache/airflow/pull/45270
<https://github.com/apache/airflow/pull/45106>>
PR #45062: Add dry run for backfill <
https://github.com/apache/airflow/pull/45062
<https://github.com/apache/airflow/pull/44899>>
Please reply to this thread with your selection or offer your own
nominee(s).
Voting will close on Friday, January 31st at 10 AM PST. The winner(s) will
be featured in the next issue of the Airflow newsletter.
Also, if there’s an article or event that you think should be included in
this or a future issue of the newsletter, please drop me a line at <
briana.okyere@astronomer.io>
P.S. we identified an issue with the PR of the Month Script last October <
https://lists.apache.org/thread/w6gvqojobbslt2y0qjl6yvdrvnks418c> that Jed
will be opening a PR for shortly to address.
--
Briana Okyere
Re: [VOTE] January 2024 PR of the Month
Posted by Nick Johnson <un...@icloud.com.INVALID>.
Yaweha
> On 28 Jan 2025, at 7:13 PM, Vishnu Chilukoori <vi...@gmail.com>
> wrote:
>
>
> +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 sustainability.
>
> Also, echoing Jens—great work from Wei on the new fragment cleanup and
> vatsrahul1001 for pushing the JSON conf migration over the line. Lots of
> important contributions this month!
>
> Cheers,
> Vishnu Chilukoori
>
> On Tue, Jan 28, 2025 at 12:06 PM Jens Scheffler <j_...@gmx.de.invalid>
> wrote:
>
>
>
>> +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 *vatsrahul1001 <https://github.com/vatsrahul1001> to make
>
>
>> the JSON conf migration over the finish line!*
>
>
>>
>
>
>> *Jens
>
>
>> *
>
>
>>
>
>
>> On 28.01.25 15:21, Vincent Beck wrote:
>
>
>> > +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 and touted (and people working on them collectively and
>
>
>> > > individually) when we go to release announcements, and - especially -
>
>
>> > > Airflow Summit talks and new users using our features (yes Airflow
>
>
>> Summit
>
>
>> > > is coming this fall and we are announcing it this week !!!)
>
>
>> > >
>
>
>> > > But there is a big value in all the "groundwork", where there are
things
>
>
>> > > that are either slowing us down because they have not been touched for
>
>
>> > > years or introduce security risks or simply block us from making more
>
>
>> > > modern and bolder moves. This work is often unappreciated and goes
>
>
>> > > below-the-radar, so a little appreciation of those things goes a long
>
>
>> way.
>
>
>> > > Great job Shahar!
>
>
>> > >
>
>
>> > > Also this is but the beginning of the Doc build improvement work we
>
>
>> MUST do
>
>
>> > > now. The Sphinx migration has been attempted like 4 (!) times in the
>
>
>> past
>
>
>> > > and the efforts generally stalled every time, this time Shahar made it
>
>
>> > > (with a little help for Jens and myself). And we have more things
>
>
>> coming on
>
>
>> > > the doc building and publishing, which we will also have a chance to
>
>
>> > > appreciate next month I hope - we are on a good track with Pavan's hard
>
>
>> > > work and Ash's ideas and input to finally get rid of sub-hour doc build
>
>
>> > > times and big risk that our Docs will finally stop working. That
>
>
>> includes
>
>
>> > > introducing (mandatory by the ASF as of end of February) Privacy
Content
>
>
>> > > Security Policies that ASF will start enforcing in a month - so this is
>
>
>> > > very appropriate timing that will allow us to make and publish those
>
>
>> > > necessary Doc changes - without using a lot of time (and mental
health).
>
>
>> > >
>
>
>> > > J.
>
>
>> > >
>
>
>> > >
>
>
>> > > On Tue, Jan 28, 2025 at 8:31 AM Amogh Desai<am...@gmail.com>
>
>
>> > > wrote:
>
>
>> > >
>
>
>> > > > 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<am...@gmail.com>
>
>
>> > > > wrote:
>
>
>> > > >
>
>
>> > > > > I wonder why the format of PR candidates look like this:
>
>
>> > > > >
>
>
>> > > > >
>
>
>> > > > >
>
>
>> > > > > *PR #45627: Start porting mapped task to SDK
>
>
>> > > > > <https://github.com/apache/airflow/pull/45627
>
>
>> > > > >
<https://github.com/apache/airflow/pull/45627>[<](https://xnxx.com/)[
https://xnxx.com/](https://xnxx.com/)
> > > > > https://github.com/apache/airflow/pull/44332
>
>
>> > > > > <https://github.com/apache/airflow/pull/44332>>>*
>
>
>> > > > >
>
>
>> > > > > The first one is the PR which we need, what about the second one?
It
>
>
>> > > > > doesn't seem to be related at all.
>
>
>> > > > >
>
>
>> > > > > Thanks & Regards,
>
>
>> > > > > Amogh Desai
>
>
>> > > > >
>
>
>> > > > >
>
>
>> > > > > On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <
>
>
>> jedcunningham@apache.org
>
>
>> > > > >
>
>
>> > > > > wrote:
>
>
>> > > > >
>
>
>> > > > > > Tough month! My vote goes to the sphinx upgrade, #45563.
>
>
>> > > > > >
>
>
>> > \---------------------------------------------------------------------
>
>
>> > To unsubscribe, e-mail:dev-unsubscribe@airflow.apache.org
>
>
>> > For additional commands, e-mail:dev-help@airflow.apache.org
>
>
>> >
>
>
>>
>
Re: [VOTE] January 2024 PR of the Month
Posted by Vishnu Chilukoori <vi...@gmail.com>.
+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 sustainability.
Also, echoing Jens—great work from Wei on the new fragment cleanup and
vatsrahul1001 for pushing the JSON conf migration over the line. Lots of
important contributions this month!
Cheers,
Vishnu Chilukoori
On Tue, Jan 28, 2025 at 12:06 PM Jens Scheffler <j_...@gmx.de.invalid>
wrote:
> +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 *vatsrahul1001 <https://github.com/vatsrahul1001> to make
> the JSON conf migration over the finish line!*
>
> *Jens
> *
>
> On 28.01.25 15:21, Vincent Beck wrote:
> > +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 and touted (and people working on them collectively and
> >> individually) when we go to release announcements, and - especially -
> >> Airflow Summit talks and new users using our features (yes Airflow
> Summit
> >> is coming this fall and we are announcing it this week !!!)
> >>
> >> But there is a big value in all the "groundwork", where there are things
> >> that are either slowing us down because they have not been touched for
> >> years or introduce security risks or simply block us from making more
> >> modern and bolder moves. This work is often unappreciated and goes
> >> below-the-radar, so a little appreciation of those things goes a long
> way.
> >> Great job Shahar!
> >>
> >> Also this is but the beginning of the Doc build improvement work we
> MUST do
> >> now. The Sphinx migration has been attempted like 4 (!) times in the
> past
> >> and the efforts generally stalled every time, this time Shahar made it
> >> (with a little help for Jens and myself). And we have more things
> coming on
> >> the doc building and publishing, which we will also have a chance to
> >> appreciate next month I hope - we are on a good track with Pavan's hard
> >> work and Ash's ideas and input to finally get rid of sub-hour doc build
> >> times and big risk that our Docs will finally stop working. That
> includes
> >> introducing (mandatory by the ASF as of end of February) Privacy Content
> >> Security Policies that ASF will start enforcing in a month - so this is
> >> very appropriate timing that will allow us to make and publish those
> >> necessary Doc changes - without using a lot of time (and mental health).
> >>
> >> J.
> >>
> >>
> >> On Tue, Jan 28, 2025 at 8:31 AM Amogh Desai<am...@gmail.com>
> >> wrote:
> >>
> >>> 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<am...@gmail.com>
> >>> wrote:
> >>>
> >>>> I wonder why the format of PR candidates look like this:
> >>>>
> >>>>
> >>>>
> >>>> *PR #45627: Start porting mapped task to SDK
> >>>> <https://github.com/apache/airflow/pull/45627
> >>>> <https://github.com/apache/airflow/pull/45627><
> >>> https://github.com/apache/airflow/pull/44332
> >>>> <https://github.com/apache/airflow/pull/44332>>>*
> >>>>
> >>>> The first one is the PR which we need, what about the second one? It
> >>>> doesn't seem to be related at all.
> >>>>
> >>>> Thanks & Regards,
> >>>> Amogh Desai
> >>>>
> >>>>
> >>>> On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <
> jedcunningham@apache.org
> >>>>
> >>>> wrote:
> >>>>
> >>>>> Tough month! My vote goes to the sphinx upgrade, #45563.
> >>>>>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:dev-unsubscribe@airflow.apache.org
> > For additional commands, e-mail:dev-help@airflow.apache.org
> >
>
Re: [VOTE] January 2024 PR of the Month
Posted by Jens Scheffler <j_...@gmx.de.INVALID>.
+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 *vatsrahul1001 <https://github.com/vatsrahul1001> to make
the JSON conf migration over the finish line!*
*Jens
*
On 28.01.25 15:21, Vincent Beck wrote:
> +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 and touted (and people working on them collectively and
>> individually) when we go to release announcements, and - especially -
>> Airflow Summit talks and new users using our features (yes Airflow Summit
>> is coming this fall and we are announcing it this week !!!)
>>
>> But there is a big value in all the "groundwork", where there are things
>> that are either slowing us down because they have not been touched for
>> years or introduce security risks or simply block us from making more
>> modern and bolder moves. This work is often unappreciated and goes
>> below-the-radar, so a little appreciation of those things goes a long way.
>> Great job Shahar!
>>
>> Also this is but the beginning of the Doc build improvement work we MUST do
>> now. The Sphinx migration has been attempted like 4 (!) times in the past
>> and the efforts generally stalled every time, this time Shahar made it
>> (with a little help for Jens and myself). And we have more things coming on
>> the doc building and publishing, which we will also have a chance to
>> appreciate next month I hope - we are on a good track with Pavan's hard
>> work and Ash's ideas and input to finally get rid of sub-hour doc build
>> times and big risk that our Docs will finally stop working. That includes
>> introducing (mandatory by the ASF as of end of February) Privacy Content
>> Security Policies that ASF will start enforcing in a month - so this is
>> very appropriate timing that will allow us to make and publish those
>> necessary Doc changes - without using a lot of time (and mental health).
>>
>> J.
>>
>>
>> On Tue, Jan 28, 2025 at 8:31 AM Amogh Desai<am...@gmail.com>
>> wrote:
>>
>>> 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<am...@gmail.com>
>>> wrote:
>>>
>>>> I wonder why the format of PR candidates look like this:
>>>>
>>>>
>>>>
>>>> *PR #45627: Start porting mapped task to SDK
>>>> <https://github.com/apache/airflow/pull/45627
>>>> <https://github.com/apache/airflow/pull/45627><
>>> https://github.com/apache/airflow/pull/44332
>>>> <https://github.com/apache/airflow/pull/44332>>>*
>>>>
>>>> The first one is the PR which we need, what about the second one? It
>>>> doesn't seem to be related at all.
>>>>
>>>> Thanks & Regards,
>>>> Amogh Desai
>>>>
>>>>
>>>> On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <jedcunningham@apache.org
>>>>
>>>> wrote:
>>>>
>>>>> Tough month! My vote goes to the sphinx upgrade, #45563.
>>>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail:dev-help@airflow.apache.org
>
Re: [VOTE] January 2024 PR of the Month
Posted by Vincent Beck <vi...@apache.org>.
+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 and touted (and people working on them collectively and
> individually) when we go to release announcements, and - especially -
> Airflow Summit talks and new users using our features (yes Airflow Summit
> is coming this fall and we are announcing it this week !!!)
>
> But there is a big value in all the "groundwork", where there are things
> that are either slowing us down because they have not been touched for
> years or introduce security risks or simply block us from making more
> modern and bolder moves. This work is often unappreciated and goes
> below-the-radar, so a little appreciation of those things goes a long way.
> Great job Shahar!
>
> Also this is but the beginning of the Doc build improvement work we MUST do
> now. The Sphinx migration has been attempted like 4 (!) times in the past
> and the efforts generally stalled every time, this time Shahar made it
> (with a little help for Jens and myself). And we have more things coming on
> the doc building and publishing, which we will also have a chance to
> appreciate next month I hope - we are on a good track with Pavan's hard
> work and Ash's ideas and input to finally get rid of sub-hour doc build
> times and big risk that our Docs will finally stop working. That includes
> introducing (mandatory by the ASF as of end of February) Privacy Content
> Security Policies that ASF will start enforcing in a month - so this is
> very appropriate timing that will allow us to make and publish those
> necessary Doc changes - without using a lot of time (and mental health).
>
> J.
>
>
> On Tue, Jan 28, 2025 at 8:31 AM Amogh Desai <am...@gmail.com>
> wrote:
>
> > 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 <am...@gmail.com>
> > wrote:
> >
> > > I wonder why the format of PR candidates look like this:
> > >
> > >
> > >
> > > *PR #45627: Start porting mapped task to SDK
> > > <https://github.com/apache/airflow/pull/45627
> > > <https://github.com/apache/airflow/pull/45627><
> > https://github.com/apache/airflow/pull/44332
> > > <https://github.com/apache/airflow/pull/44332>>>*
> > >
> > > The first one is the PR which we need, what about the second one? It
> > > doesn't seem to be related at all.
> > >
> > > Thanks & Regards,
> > > Amogh Desai
> > >
> > >
> > > On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <jedcunningham@apache.org
> > >
> > > wrote:
> > >
> > >> Tough month! My vote goes to the sphinx upgrade, #45563.
> > >>
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [VOTE] January 2024 PR of the Month
Posted by Jarek Potiuk <ja...@potiuk.com>.
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 - especially -
Airflow Summit talks and new users using our features (yes Airflow Summit
is coming this fall and we are announcing it this week !!!)
But there is a big value in all the "groundwork", where there are things
that are either slowing us down because they have not been touched for
years or introduce security risks or simply block us from making more
modern and bolder moves. This work is often unappreciated and goes
below-the-radar, so a little appreciation of those things goes a long way.
Great job Shahar!
Also this is but the beginning of the Doc build improvement work we MUST do
now. The Sphinx migration has been attempted like 4 (!) times in the past
and the efforts generally stalled every time, this time Shahar made it
(with a little help for Jens and myself). And we have more things coming on
the doc building and publishing, which we will also have a chance to
appreciate next month I hope - we are on a good track with Pavan's hard
work and Ash's ideas and input to finally get rid of sub-hour doc build
times and big risk that our Docs will finally stop working. That includes
introducing (mandatory by the ASF as of end of February) Privacy Content
Security Policies that ASF will start enforcing in a month - so this is
very appropriate timing that will allow us to make and publish those
necessary Doc changes - without using a lot of time (and mental health).
J.
On Tue, Jan 28, 2025 at 8:31 AM Amogh Desai <am...@gmail.com>
wrote:
> 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 <am...@gmail.com>
> wrote:
>
> > I wonder why the format of PR candidates look like this:
> >
> >
> >
> > *PR #45627: Start porting mapped task to SDK
> > <https://github.com/apache/airflow/pull/45627
> > <https://github.com/apache/airflow/pull/45627><
> https://github.com/apache/airflow/pull/44332
> > <https://github.com/apache/airflow/pull/44332>>>*
> >
> > The first one is the PR which we need, what about the second one? It
> > doesn't seem to be related at all.
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <jedcunningham@apache.org
> >
> > wrote:
> >
> >> Tough month! My vote goes to the sphinx upgrade, #45563.
> >>
> >
>
Re: [VOTE] January 2024 PR of the Month
Posted by Amogh Desai <am...@gmail.com>.
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 <am...@gmail.com>
wrote:
> I wonder why the format of PR candidates look like this:
>
>
>
> *PR #45627: Start porting mapped task to SDK
> <https://github.com/apache/airflow/pull/45627
> <https://github.com/apache/airflow/pull/45627><https://github.com/apache/airflow/pull/44332
> <https://github.com/apache/airflow/pull/44332>>>*
>
> The first one is the PR which we need, what about the second one? It
> doesn't seem to be related at all.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <je...@apache.org>
> wrote:
>
>> Tough month! My vote goes to the sphinx upgrade, #45563.
>>
>
Re: [VOTE] January 2024 PR of the Month
Posted by Amogh Desai <am...@gmail.com>.
I wonder why the format of PR candidates look like this:
*PR #45627: Start porting mapped task to SDK
<https://github.com/apache/airflow/pull/45627
<https://github.com/apache/airflow/pull/45627><https://github.com/apache/airflow/pull/44332
<https://github.com/apache/airflow/pull/44332>>>*
The first one is the PR which we need, what about the second one? It
doesn't seem to be related at all.
Thanks & Regards,
Amogh Desai
On Tue, Jan 28, 2025 at 4:31 AM Jed Cunningham <je...@apache.org>
wrote:
> Tough month! My vote goes to the sphinx upgrade, #45563.
>
Re: [VOTE] January 2024 PR of the Month
Posted by Jed Cunningham <je...@apache.org>.
Tough month! My vote goes to the sphinx upgrade, #45563.
Re: [VOTE] January 2024 PR of the Month
Posted by Jed Cunningham <je...@apache.org>.
We had 4 PRs that were tagged PROTM
<https://github.com/apache/airflow/pulls?q=is%3Apr+merged%3A2025-01-01..2025-01-27+is%3Aclosed+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/45563
PR #45678: Update existing significant newsfragments with the later
introduced template format
https://github.com/apache/airflow/pull/45678
PR #45729: Remove dag processor from the scheduler
https://github.com/apache/airflow/pull/45729
Re: [VOTE] January 2024 PR of the Month
Posted by Wei Lee <we...@gmail.com>.
#45563 +1, this is awesome! and thanks all for mentioning #45678
Best,
Wei
> On Jan 31, 2025, at 1:42 PM, Shahar Epstein <sh...@apache.org> 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 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, 2025 at 12:45 AM Briana Okyere
> <br...@astronomer.io.invalid> wrote:
>
>> 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/airflow/pull/45627
>> <https://github.com/apache/airflow/pull/44332>>
>>
>> PR #45924: AIP-72: Port Registering of Asset Changes to Task SDK on task
>> completion <https://github.com/apache/airflow/pull/45924
>> <https://github.com/apache/airflow/pull/44972>>
>>
>> PR #44533: Update conf column in dag_run table type from bytes to JSON <
>> https://github.com/apache/airflow/pull/44533
>> <https://github.com/apache/airflow/pull/44712>>
>>
>> PR #45270: Migrate trigger form params to new UI <
>> https://github.com/apache/airflow/pull/45270
>> <https://github.com/apache/airflow/pull/45106>>
>>
>> PR #45062: Add dry run for backfill <
>> https://github.com/apache/airflow/pull/45062
>> <https://github.com/apache/airflow/pull/44899>>
>>
>> Please reply to this thread with your selection or offer your own
>> nominee(s).
>>
>> Voting will close on Friday, January 31st at 10 AM PST. The winner(s) will
>> be featured in the next issue of the Airflow newsletter.
>>
>> Also, if there’s an article or event that you think should be included in
>> this or a future issue of the newsletter, please drop me a line at <
>> briana.okyere@astronomer.io>
>>
>> P.S. we identified an issue with the PR of the Month Script last October <
>> https://lists.apache.org/thread/w6gvqojobbslt2y0qjl6yvdrvnks418c> that Jed
>> will be opening a PR for shortly to address.
>>
>> --
>> Briana Okyere
>>
Re: [VOTE] January 2024 PR of the Month
Posted by Shahar Epstein <sh...@apache.org>.
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, 2025 at 12:45 AM Briana Okyere
<br...@astronomer.io.invalid> wrote:
> 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/airflow/pull/45627
> <https://github.com/apache/airflow/pull/44332>>
>
> PR #45924: AIP-72: Port Registering of Asset Changes to Task SDK on task
> completion <https://github.com/apache/airflow/pull/45924
> <https://github.com/apache/airflow/pull/44972>>
>
> PR #44533: Update conf column in dag_run table type from bytes to JSON <
> https://github.com/apache/airflow/pull/44533
> <https://github.com/apache/airflow/pull/44712>>
>
> PR #45270: Migrate trigger form params to new UI <
> https://github.com/apache/airflow/pull/45270
> <https://github.com/apache/airflow/pull/45106>>
>
> PR #45062: Add dry run for backfill <
> https://github.com/apache/airflow/pull/45062
> <https://github.com/apache/airflow/pull/44899>>
>
> Please reply to this thread with your selection or offer your own
> nominee(s).
>
> Voting will close on Friday, January 31st at 10 AM PST. The winner(s) will
> be featured in the next issue of the Airflow newsletter.
>
> Also, if there’s an article or event that you think should be included in
> this or a future issue of the newsletter, please drop me a line at <
> briana.okyere@astronomer.io>
>
> P.S. we identified an issue with the PR of the Month Script last October <
> https://lists.apache.org/thread/w6gvqojobbslt2y0qjl6yvdrvnks418c> that Jed
> will be opening a PR for shortly to address.
>
> --
> Briana Okyere
>