Re: Proposal: Abandoning monolithic Boost documentation.

From: Peter Dimov (pdimov_at_[hidden])
Date: 2025-04-18 17:41:03

Sam Darwin wrote:
> > The main problem that was raised is that a failure in one library
> > causes
> all the docs to disappear.
> > No longer missing docs from problems in individual libraries.
> 
> There is a meaningful advantage to that "problem" though. Right now
> boostorg/pfr docs are failing.  Peter and I commented to the author. This
> morning I submitted a bug fix which is just waiting to be merged.
> Imagine the alternative: a mostly-unmaintained library starts to have doc
> failures.  The 'superproject' continues to build fine. Nobody sees the issue as
> particularly important.  Perhaps someone notices, but think "it's that
> maintainer's responsibility". The next thing you know, it's time for a boost
> release and the library's docs will not be included in the official archive since
> they are not building.

This is an advantage when doing releases, but very much a disadvantage
when one just wants to work on one's own docs and see the result on boost.org.

Also, the failure notifications go to the wrong people (you and me), rather
than to the maintainers. But that's probably unavoidable either way.