Woohoo! 🎉
--
Regards,
Aritra Basu
On Sat, 30 Aug 2025, 8:32 pm Jarek Potiuk, wrote:
> The https://github.com/apache/airflow/pull/53770 ("Migrated prod builds to
> use python built from source") has been merged. This means that our PROD
> images built from main (soon 3.1) will get the latest rel
Thanks to Aritra for leading it !!!
On Sat, Aug 30, 2025 at 5:27 PM Aritra Basu
wrote:
> Woohoo! 🎉
> --
> Regards,
> Aritra Basu
>
> On Sat, 30 Aug 2025, 8:32 pm Jarek Potiuk, wrote:
>
> > The https://github.com/apache/airflow/pull/53770 ("Migrated prod builds
> to
> > use python built from sou
> I would say we should only worry about backcompat when there's something
to
worry about.
I think Daniel is quite right. In this case what **would** happen if
someone relies on `try AirflowException`, the issue would be immediate to
see and easy to fix (and we can describe it in release notes as
The https://github.com/apache/airflow/pull/53770 ("Migrated prod builds to
use python built from source") has been merged. This means that our PROD
images built from main (soon 3.1) will get the latest released Python
packages directly from the PSF release server and we build Python from
sources.
* A: I also think that we should **just** make sure we have no abuse.
Having a willing translator (like Eloi) who we know and trust and who can
take responsibility to make it "good" is enough - and doing just auto
translation back to check for potential abuse should be enough. And
sponsors should d
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”
