Also the remaining tasks are now nicely described as the cool new sub-issues in https://github.com/orgs/apache/projects/403/views/2?pane=issue&itemId=88615825&issue=apache%7Cairflow%7C44373
On Mon, Jan 13, 2025 at 5:01 PM Ash Berlin-Taylor <a...@apache.org> wrote: > Lovely, I think being able to use latest sphinx-autoapi features will make > my life easier rendering docs for AIP-72’s Task SDK too > > -a > > > On 13 Jan 2025, at 08:11, Pavankumar Gopidesu <gopidesupa...@gmail.com> > wrote: > > > > Woohoo 🎉 great job Jarek, Shahar , Jens. > > > > We are on track :) > > > > > > Regards, > > Pavan > > > > On Mon, Jan 13, 2025, 06:52 Shahar Epstein <sha...@apache.org> wrote: > > > >> I was happy to take part in upgrading Sphinx! The last Dev call > triggered > >> me to do something about it :) > >> > >> It was plenty of trial and error until we've figured out how to solve > all > >> of the Sphinx riddles, but I'm glad that we've finally made it. > >> > >> Big thanks to Jarek and Jens for supporting! Hopefully mypy is happy > with > >> all of the Drachenfutter we gave it ;) > >> > >> > >> Shahar > >> > >> > >> On Mon, Jan 13, 2025, 00:37 Jarek Potiuk <ja...@potiuk.com> wrote: > >> > >>> Hey here. > >>> > >>> Led by Shahar (kudos!) and with Jens's and a little of my help we > finally > >>> got the first part of doc improvement done. We updated our > >> Sphinx/docutils > >>> to Sphinx 8.1.3 finally in main (latest version released in October > 2024 > >> as > >>> opposed to 6.2.1 which we had before - released August 2023 !) - this > >> took > >>> a few tries before, and finally we got it working and merged both > >> Airflow 3 > >>> build and v2-10-test backport (we had to change Python 3.9 to be > default > >>> there). > >>> > >>> This also unblocked upgrades of a few dependencies that will help us to > >>> deal with security issues / supply chain. > >>> > >>> The docs look slightly different (mostly links) but it is good > otherwise. > >>> > >>> We have a few more things to do - Pavan looks at the S3 offloading of > >>> historical versions, and we need to heavily modernize the > "airflow-site" > >>> build process (and rethink the way sphinx-airflow-theme is built - > >>> possibly with the use of `uv workspaces` - similarly as in > >>> providers/tasl_sdk. > >>> > >>> But we made nice progress ! > >>> > >>> J. > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >