Release Notes in a Consistent Location

[Arcturus]

I was partway through deploying 3.0.256 (Master) to the dozen PW sites I manage when I saw there's now a 3.0.257 (Master).

What's the difference? NO IDEA

I checked the website, the blog, the forums, GitHub... because the clues are typically never in the same place or format, and there's not a single sentence describing what's new.

Is it the same as 3.0.257 (Dev), but proven? NO IDEA

Should I start my process over? NO IDEA
 

I appreciate that no one likes doing documentation, but this has been an issue for years, and I'm not asking for much. Looking at LightSpeed Web Server, they have a basic, designated page that gets a low-effort bullet list with every release. This would suffice for the majority of us. Missed a few versions? You can get the gist of things within a couple of minutes. It should live within the Download section of the main website.



It would be even better if someone circled back later and linked to a blog, forum, API doc, etc., if elaboration is available for a bullet point... but I'll take what I can get, as long as it's better than the current ad-hoc approach.

[elabx]

Agree! Maybe it could be automated with GitHub actions? Something that at least gets a list of commits?

[Peter Knight]

It’s a very simple task these days too. I have all changelog and release notes created automatically via a loop. With a few editing guidelines and some samples, it pretty much runs on auto pilot.

Finish feature > automation script reads > rules etc