Please use less AI for writing release notes

[Jon-dog]

I understand writing release notes can be annoying or a struggle, but many LLMs write in an overly positive style. This leads to false expectations/hype and makes changes like "I added a drop shadow/fixed an off by one error" sound like something much grander.

A recent example of this is the "UTC Anchor principle", which is not a real phrase. Release notes are also made longer to read due to the bolded leading phrases: and singular changes/features being mentioned multiple times, but slightly differently.

I want to be able to understand what has been fixed or added that actually matters and is worded in a way that connects to the reality of the plugin, not something an AI cooked up.

Edit: this change isn't even real
"The settings UI now documents all 40+ available template variables for easy reference."

The UI only shows 12

[callumalpass]

Thanks for raising this and apologies @Jon-dog . I can work on that!

When I first started working on this plugin I wasn't writing release notes. As people started using it I thought I should include them with releases, and have been taking the easy route! Now that there is a good number of people using this plugin, I can certainly put more time and effort into the release notes.

[callumalpass]

I'll just add that the 'UTC Anchor Principle' is referring to an idea internal to the codebase (see commit b4d52c7)--though I admit that this is not helpful for most people reading the release notes.

[callumalpass]

And the "40+ template variables" are documented in the filename templating section, not the body template section (you have to disable "Store title exclusively in filename" and make the "Filename format" = "Custom template"). There are 40 variables, so the '+' is misleading.

[callumalpass]

[Jon-dog]

Thank you for being receptive to this :)

I took a look through the settings to make sure I didn't miss block of template variables. Guess I missed that one because I do store the title in the filename haha