rhuss commented on issue #354: Automatically add release notes on github releases URL: https://github.com/apache/camel-k/issues/354#issuecomment-456560228 Tbh, I still collect the high-level changes manually in a top-level CHANGELOG and verify for each PR that it contains an entry in the changelog if its a relevant PR. I experimented with auto extracting from commit message, but this requires a level of commit discipline I never ever have seen in a community project with PR contributions from the outside. Of course, one can insist on rewriting the commit messages when reviewing a PR but at the end, this was just tedious. I have to confess that even for PRs which are missing a changelog entry, I often approve the PR to avoid yet another turnaround and edit the changelog directly on upstream master via the GitHub Web UI, adding a line to the Changelog directly. Example of a changelog maintained this way is https://github.com/fabric8io/docker-maven-plugin/blob/master/doc/changelog.md (the links are created via a script during a release when entering I just add the plain issues/pr number without the link). 'happy to do it differently, but as mentioned, educating people to use a fixed format for the commit messages is a challenge on its own (where I've failed multiple times, think e.g. how we tried to introduce commitizen style logs in the Syndesis project).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
