Re: [boost] New Boost Website: Open to Volunteers!

On the topic of release notes, if the library author prefers to customize and format the text, then being tied precisely to tagged git commit messages could be overly restrictive, but it's a possibility and more automated. Another option, of having a meta/changelog.json file, is an idea. It would be important to require the formatting of that file to include the release version, every time, so earlier notes don't automatically get pulled into later releases. The processing of the Release Notes is tied to the website, more than to release-tools.. So, a change to the process could be part of the 'New Boost Website'. Or, add it later on: "limiting the scope of new features for the initial release." On Sat, Apr 16, 2022 at 4:53 PM Vinnie Falco via Boost < boost@lists.boost.org> wrote:

On Sat, Apr 16, 2022 at 2:49 PM Peter Dimov via Boost wrote:

...

We could, e.g. have meta/changelog.json in each library that holds the per-library changes, and generate the release notes from that.

Yes that is possible although it has more to do with the release process (which Sam maintains).

Sam?

Thanks

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost