Hook changelogs in release notes
Currently, we describe the changes provided in the hooks in the changelog in the main repository. It is pretty convenient because, anyway, we need to update the hook submodule reference to the main repository if any changes were provided there. But the hooks contain their own changelogs but they are not used in the release process. In Kea, we present them together with release notes. @andrei proposed to do the same in Stork in !716 (comment 432749) .
Kea has only one repository for all hooks. It means there is only one changelog for all hooks, so in total, there are two changelogs (main and hooks) to maintain. In Stork, we plan to store every hook in a separate repository. Finally, you will have multiple changelogs that need to be processed to prepare the release notes. As far as I know, it is mainly a manual job, right? So, realizing this idea may increase the complexity work of release engineers.
We can extend the release utilities in the main repository to automate including the hook changelogs in the release notes.