On 27/01/2023 11:40 am, Henry Wang wrote: > Hi Andrew, > >> -----Original Message----- >> From: Andrew Cooper <[email protected]> >> Subject: [PATCH] Changelog: Add details about new features for SPR >> >> Signed-off-by: Andrew Cooper <[email protected]> > Thanks for remembering this :) > > Acked-by: Henry Wang <[email protected]>
Thanks. I'll commit this when OSSTest has become unblocked. > >> --- >> A reminder to everyone, write the changelog as it happens, rather than >> scrambling to remember 8 months of development just as the release is >> happening. > I wonder if there is a way to automate this in our CI so we can avoid > forgetting this. But currently I am not really sure if the solution in my mind > is simple enough... I will try to keep this issue in my mind so that probably > I > can come back with some solutions. The automated version is `git log $PREV_RELEASE > changelog.log`, and this is very deliberately not that. It needs the maintainers / committers to keep "interesting user visible changes" in mind at some point after the patches have gone in, are logically complete, and have been around long enough that major catastrophes (i.e. those liable to incur a full revert) are likely to have happened. But I would like to stress. While it is the Release Maintainer's job to make sure this gets done, it is not the Release Maintainers job to write it. That is an unreasonable burden. ~Andrew
