Changelogs - running, betas, or otherwise?

AI-generated summary

In a discussion titled “Changelogs - running, betas, or otherwise?” under the Support category, users seek clarity on Discourse’s changelog practices and versioning. mreach asks if there’s a running changelog or roadmap for development, noting beta releases lack visible changelogs on GitHub. awesomerobot clarifies that Discourse maintains release notes and roadmaps on Meta, not GitHub, directing users to Meta’s releases category and release notes tag. mreach suggests adding a GitHub link for easier discovery. dscat questions why minor releases (e.g., 2.6.7) lack detailed notes, especially for security fixes, requiring manual commit comparison. awesomerobot is confused by this need if notes already mention security fixes. Falco explains that stable branch releases don’t get formal notes but only include critical bug or security backports — users should always upgrade. dscat asks how minor vs. tiny releases differ, assuming semantic versioning (Major.Minor.Patch). jomaxro notes Discourse doesn’t use those terms, and jomaxro clarifies they don’t follow semantic versioning strictly — versions are milestones, and sites can update to any recent code (e.g., Meta runs 153 commits ahead of 2.8.0.beta1). Falco and jomaxro emphasize continual development over rigid versioning.

I frequently like to follow what’s going on with Discourse development. Is there a running changelog that shows current things being implemented or a roadmap?

Do beta snapshots have a changelog that I’m missing?

For example, on the current beta release, I don’t see any kind of changelog associated with the release page or even on the source repo branch…

We keep everything here on Meta rather than Github.

You can see an outline of all our major releases here, and what’s currently planned for future releases: https://meta.discourse.org/c/releases

We post release notes here: Topics tagged release-notes

Thank you very much for clarifying. It might be helpful to also link to this on GitHub so that folks can find it readily via a “Changelog” link near the top as I’ve seen in other projects.

Why there aren’t any posts for smaller changes?, ie: 2.6.7 release notes had a security fix.
I have to compare tags to see the commits to verify there were security fixes

Sorry I’m not sure I’m following… if the release notes said there was a security fix, why did you have to compare tags?

We don’t do release notes for the stable branch, but we also only backport major bug fixes or security issues, so the answer to the question “Should I update to a newer point release while running the ‘stable’ branch?” is always yes.

So how do minor and tiny releases differentiate?
ie: are tiny releases bug fixes and security only?
are minor releases new features or something else?

It seems based on @Falco post, no matter which release it is, we should always upgrade

Define minor and tiny releases - not sure we use those terms.

I was wondering if you guys were following similar semantic versioning as in https://semver.org/.
ie: 2.6.7 would be Major.Minor.(Tiny or Patch)

We do not strictly follow semantic versioning, no. We practice continual development. Version numbers function more as milestones than as strict semantic versioning. By default, sites can update to the most recent code at any time, they’re not restricted to a specific “release”. For example, right now Meta is running 153 commits ahead of the “2.8.0.beta1” release.