Re: [boost] Docs in release tarballs

In the beginning, when dinosaurs roamed the Earth, documentation consisted of each library having a heap of .html files in its directory, following no convention in either naming or placement. So there was no way to have a separate tarball with the docs, but there wasn't any need either, because Boost was much smaller.

Does that mean that dinosaurs still roam around here? :) Is there any reason as of today to keep doing it? (other than no-one volunteering to make the change). I guess there must be, since we have separate no-docs GitHub releases. Regards, Ruben.