Tracking the "Fixed in release" on the JIRA tickets would take care about any gaps pretty much automatically. In general it's a good idea for an RM to run a spring-cleaning on the JIRA tickets to scope up the release. Then once all tickets are fixed, you can simply _generate_ the release notes with a single-button click.
Cos On Mon, Aug 01, 2016 at 01:43PM, Pavel Tupitsyn wrote: > Igniters, > > RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. There > are likely more noteworthy changes since 1.6. > > Let's discuss the changes to be included in release notes and fix them. > > Please reply to this email with your proposals. > > Pavel.
