On 4/16/20 2:38 PM, Albert Astals Cid wrote:
Kind of yeah. Or use the "raw" changelogs we create for the releases, though
depending on when the features are needed and when the changelogs are created may not
give much time for writing the features.
For the release service releases we already parse CHANGELOG
https://cgit.kde.org/sysadmin/release-tools.git/tree/create_log.py#n135
But the only thing we do right now is use that text for the changelog file
instead of the first line of the commit.
It may make sense to highlight them a bit more somehow, suggestions welcome i
guess.
The promo people just need a list of all CHANGELOG entries in a release
so they can rewrite it in more human-friendly terms. Right now this is
done manually by me and others by looking through commit logs and blog
posts and adding the equivalent of CHANGELOG text into an
etherpad/share.kde.org document. Automating that somehow would be nice.
Nate
