Continuing the discussion from Gramps v5.2.0-beta1 released:
@Nick-Hall Could you swap in the above text into your 5.2 announcement? Since 5.2 documentation hasn’t made it to the wiki, people will want to read the development discussion to determine if they found a bug or misunderstood the feature.
Can the insertion be added to whatever generates your lists? More specific info will probably be needed for the final 5.2 Release notice too.
For everyone, I will try to do a posting with each section of the Announcement as an anchor for threaded discussions. Then backfill the links.
The ChangeLog is created automatically from the commit messages. Then I edit it manually to create the NEWS file. Finally, I add some markdown when creating the release announcements.
The release announcement on Github is then used as a basis for other announcements.
Is it possible to tweak the underlying data that drives the commit messages? The “strikethrough, superscript & subscript” message won’t be any more obvious that it is a Note Editor enhancement when the release notes for the final candidate are generated.
And from the sheer volume of changes, there are hundreds of WikiContributor workhours before it will adequately cover 5.2 release. So, at least in the beginning, bullet points in the release notes will probably need to point to the PR or feature request discussions.
- MantisBT 5.2 Roadmap (only 33 items listed as of July 2023)
- GitHub 5.2 milestones
I knew being at my normal level of anal retentiveness would hurt me! 
It already kept me from learning enough to finish updating the copy of the “What’s next?” gramplet that would’ve helped Newbies.
No. Once they are merged they cannot be changed.
Good commit messages are important as described in our committing policies.
We can always re-write release announcements though. You can write the 5.2.0 release announcement for me if you want.
I am still discovering initial column widths in Object Editor tabs that are too small by default. Have they been validated in all object editors? Do we have a checklist of Object (and Object Reference) Editors and their tabs?
Do we need to test persistence as well as the initial value? And what about things that might affect that persistence? (Like a change in the virtual monitor layout and size. There was a Windows issue resolved several years ago where dialogs could restore off-screen when extra monitors had been disconnected.)
In 5.2.1, the Media Reference Editor has Source Citation, Attributes, Notes tabs with columns sized to minimum widths rather than any reasonable width for content:
5.2 Highlights bullets:
- Make the tab columns resizable. Implements #8767