For a long time, the release notes for the stable branch mainly contained security fixes and occasionally a few other commits. This also applied to plugins, as they were all pinned at the beginning of a new release cycle.
https://github.com/discourse/discourse-solved/commit/2db5b45af6c52507299d64be066aaf3c4d3b4188
So, the release notes for stable were quite short [example], and those for beta/tests-passed were more extensive with descriptions of new features and an “Even more” part [example].
Since February, however, that “Even more” section has also appeared in all stable release notes [example]. Does this mean that, from that point on, all new features in plugins have become directly available to users on the stable branch? I thought plugin versions were still pinned.
https://github.com/discourse/discourse-solved/commit/9a00198d4b0bb8d19f6714550b2435c0841e251b
Given how I understand pinning, I’m probably missing something here - the inclusion of recent plugin commits in the stable release notes doesn’t make sense for me.
Could someone help me see what I’m misunderstanding?
AI-generated summary
Moin is confused about recent changes to Discourse’s stable release notes. Previously, stable releases only listed security fixes and occasionally minor updates, while beta/tests-passed releases included detailed descriptions of new features and an “Even more” section. Since February, however, the “Even more” section has appeared in stable release notes too — including recent plugin commits — which suggests new plugin features are now available on stable. But Moin thought plugin versions were still pinned at the start of each release cycle, making this inclusion puzzling. They’re asking for clarification on what they’re misunderstanding regarding plugin pinning and release note content.
4 Likes