-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature #2821 prepare v6.0.0 release #2843
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend moving a few items from the "Internal" section to the "Documentation" section. I'd also recommend renaming "Internal" as "Repository, build, and test" for consistency with the section in the MET release notes and to provide a little more description of those issue types.
The other release notes look fine and are basically just the titles of the source issues. In general, I'd seek more consistency in issue title naming conventions to make them more easily digestible and understood.
I like it when...
- Bugfix titles are "Fix ABC to do XYZ".
- Enhancement titles are "Enhance ABC to do XYZ" (or "Add ABC to XYZ")
- And so on.
With lots of people writing lots of titles, we're going to get lots of variations in the conventions. I think the process of drafting the release notes is to seek more standardization and consisency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @georgemccabe. Thanks for making these updates.
I approve.
Review release notes: https://metplus--2843.org.readthedocs.build/en/2843/Users_Guide/release-notes.html#metplus-version-6-0-0-release-notes-2024-12-18