Re: [boost] Docs in release tarballs

I think, an archive that includes at least tests is useful for third party CI. And some libraries also build examples as part of their test suites, so those should be included as well.

This is the case yes. For automated installation using EasyBuild (similar to Spack) the tests of the software are run after building to ensure everything works in the current environment.

Perhaps, we could publish three variants: full, source-only (which includes tests and examples but not docs) and minimal (which only includes library sources)? Makes sense to me