Hi all! Happy to say this:
*1. We drop pdf builds in CI, the release process and the Docker image, but keep support in the code base.* *2. Rohit volunteered to maintain the pdf build, so if he (or another person we know and trust to receive artifacts from and distribute them) wants to send PRs to fix doc build issues and merge a pdf build into https://github.com/numpy/doc/ <https://github.com/numpy/doc/>, we'll review and merge those.* is exactly the proposal that came up from the documentation team meeting today :) We also proposed circling back in the next docs team meeting in two weeks if there are any hiccups, but there was consensus at the meeting that this is a good compromise. - Melissa On Mon, May 23, 2022 at 4:33 PM Stefan van der Walt <[email protected]> wrote: > On Mon, May 23, 2022, at 10:34, Ralf Gommers wrote: > > I'm not so interested in the detailed discussion later on in this thread > to be honest. Let me propose a simple solution that should make everyone > happy: > 1. We drop pdf builds in CI, the release process and the Docker image, but > keep support in the code base. > 2. Rohit volunteered to maintain the pdf build, so if he (or another > person we know and trust to receive artifacts from and distribute them) > wants to send PRs to fix doc build issues and merge a pdf build into > https://github.com/numpy/doc/, we'll review and merge those. > > > I second this proposal. Maybe with the provision that if, in a year from > now, the PDF build is in a broken / unmaintained state, we remove it > completely. > > Stéfan > > _______________________________________________ > NumPy-Discussion mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: [email protected] >
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: [email protected]
