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 <amoghdesai....@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 <amoghdesai....@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 <jedcunning...@apache.org
> >
> > wrote:
> >
> >> Tough month! My vote goes to the sphinx upgrade, #45563.
> >>
> >
>

Reply via email to