There’s need to generate release notes for each release and the process should be automated or at least described in some way.
After thinking a bit I came up with following idea:
Each developer/(project member) can nominate any issue to be included into release notes.
To do so they (or product manager/other project member) assign scoped label to the issue (like
Optional: Automation/CI/script goes to each such issue and post information request there with the template to be filled in and changes scope to
release_notes::input_needed. This step will save Dev’s time on looking into documentation for this template
Once developer see this label they put information needed into comment using template and change scope to
Automation/CI/script/release engineer uses provided information to generate release notes entry from it. ( Or put gentle reminders if the release is approaching but information was not provided )
This should allow to save time before the release itself and spread documentation phase across whole development cycle.
Template itself TBD but it should not take more than 5 minutes to fill it in.
The process can be easily scaled to generate other release-related documentation (known issues, fixed bugs etc)