On Sat, Dec 14, 2024 at 6:13 AM Vinnie Falco via Boost < boost@lists.boost.org> wrote:
We are proud to publish the first Boost Release Report, for 1.87.0. This report is designed to showcase and credit the work of the many volunteers who contribute to the libraries and other things in Boost, published as an official release three times a year.
https://downloads.cppalliance.org/reports/boost_1_87_0_release_report.pdf
I appreciate the effort, but the stats feel a bit like counting productivity in terms of LOC. Neither the amount of commits nor posts tell me anything about their content. That is, the first two pages would suffice. What are you trying to communicate with pages 3-98? If you want to write a release report, I think it should not be auto-generated (except for maybe the first page), but editorialized highlights. E.g. it could summarize the review of a library and the library in the release (boost parser in this case). Or, even better, it could put a spotlight on recent improvements/changes in a library, e.g. I could help write something when asio has some major additions.
Thanks
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost