Boost logo

Boost :

From: James E. King III (jking_at_[hidden])
Date: 2022-04-16 21:56:33

On Sat, Apr 16, 2022 at 5:49 PM Peter Dimov via Boost
<boost_at_[hidden]> wrote:
> Vinnie Falco wrote:
> > We are adding a database, and this kind of feature will be possible in theory.
> > But, in order to ensure that we actually get this thing done we are limiting the
> > scope of new features for the initial release. We aren't touching the
> > documentation and we are striving to make few to no changes in how the
> > release notes are published.
> Fixing the way the release notes are published would be pretty useful.
> We could, e.g. have meta/changelog.json in each library that holds the
> per-library changes, and generate the release notes from that.

I have to disagree with that. GitHub provides us with labels, and people should
be using reasonable check-in comments. Instead of having a single
collision file
like changelog (I have seen this on django-simple-history and it isn't
pretty) it would
be much better to have a label for a commit that should be included in
the release
notes and pull the first line of that commit into the release notes
with a link to the
pull request that it was associated with. This would be more
automated and cause
far less commit collisions. Using a label like `release-note-worthy`
to faciliate this
would also allow a project maintainer to decide what is worthy by
modifying the labels.

- Jim

Boost list run by bdawes at, gregod at, cpdaniel at, john at