Thanks for sharing that Jarek!

I hadn't seen that issue and PR, was indeed great to see the collaboration.
Love it :)

Vikram


On Mon, Oct 20, 2025 at 8:49 PM Jarek Potiuk <[email protected]> wrote:

> Indeed ... I saw a lot of the problem "being solved" - also I think
> triaging of new issues is now faster and we try to assess the applicability
> for 3.0 and actively finding/linking duplicates by triagers, also I see
> huge help from the users - like the memory issue that was not only well
> diagnosed with the help of the users (with memray) but also we have this PR
> https://github.com/apache/airflow/pull/56821 -> where the user (Joe) who
> did the investigation https://github.com/apache/airflow/issues/56879 is
> adding a tooling to Airflow to make it easier for other users to provide
> more insights into memory issues.
>
> This is what I call a true collaboration spirit where every community
> member can help as much as they can to improve stability and make airflow 3
> rock-solid.
>
> Way to go :) .
>
> J.
>
>
> On Mon, Oct 20, 2025 at 9:28 PM Ferruzzi, Dennis <[email protected]>
> wrote:
>
>> Great work!
>>
>>
>>  - ferruzzi
>>
>>
>> ________________________________
>> From: Vikram Koka via dev <[email protected]>
>> Sent: Monday, October 20, 2025 12:07 PM
>> To: [email protected]
>> Cc: Vikram Koka
>> Subject: RE: [EXT] Airflow 3.1.1 and 3.1.2
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you can confirm the sender and know
>> the content is safe.
>>
>>
>>
>> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
>> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez
>> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que
>> le contenu ne présente aucun risque.
>>
>>
>>
>> Thanks Kaxil, that's great to hear.
>>
>> Just to add some details around this, there are around 130 issues closed
>> for the 3.1.1 milestone at this time.
>>
>> Taking out internal issues such as dev-tooling, there are around 120
>> Github
>> issues closed in this patch release.
>> These are broken down as follows:
>> - UI: 57, about 48%
>> - API: 24, about 20%
>> - Most of the rest are in core: about 40%
>>
>> Just to reiterate, this is based on Github issues, not PRs.
>>
>> Best regards,
>> Vikram
>>
>> On Mon, Oct 20, 2025 at 4:35 AM Kaxil Naik <[email protected]> wrote:
>>
>> > Hellow all,
>> >
>> > I am planning to cut 3.1.1rc1 tonight or tomorrow morning to get some of
>> > the critical bug fixes out.
>> >
>> > And then following it up with 3.1.2 on/before 31st October -- before I
>> got
>> > on leave.
>> >
>> > Please priortize fixing bugs and get the PRs reviewed/merged.
>> >
>> > Regards,
>> > Kaxil
>> >
>>
>

Reply via email to