LONGTAIL FORGE CHANGELOG
The detailed record of what changed.
The Longtail Forge Changelog is the versioned record: what shipped, what changed, what was fixed, and when it happened.
If you would rather get the useful part without reading release-by-release detail, Longtail Forge Updates turns recent development into periodic, human-friendly summaries focused on the practical impact.
THREE DIFFERENT JOBS
Updates, changelog, and roadmap answer different questions.
Keeping them separate makes each one more useful. You should not have to read a technical release record to understand the direction of the product, and a changelog should not become a marketing recap.
Longtail Forge Updates
The readable digest. Recent development is grouped into meaningful themes and explained in terms of what changed, why it matters, and what someone using Longtail Forge would actually notice.
Changelog
The detailed record. Versions, dates, additions, behavior changes, fixes, and other release-level facts belong here so there is something concrete to reference later.
Roadmap
The forward-looking view. It covers what is being worked on, what is likely to come next, and what is intentionally not being treated as a promise with a fake deadline attached.
HOW TO READ THE CHANGELOG
Specific enough to be useful later.
The changelog is allowed to be more detailed than the periodic Updates posts. Its job is to preserve release-level facts accurately enough that a version number, bug report, support question, or “when did that change?” conversation has a reliable reference point.
Added
New capabilities that became available in a release, described clearly enough to identify the feature and the version where it appeared.
Changed
Existing behavior that works differently now, especially anything likely to matter to someone already using, testing, administering, or integrating with Longtail Forge.
Fixed
Bugs and rough edges that were resolved, with enough description to recognize the symptom without needing the implementation details behind the fix.
Not every release needs every heading. If a version only fixes things, the changelog can say what it fixed and move on. No empty ceremony required.
PUBLIC RELEASE NOTES
Release history will stay here. The readable story lives in Updates.
Longtail Forge is still moving through active development, where internal builds can change several times in a day. Public release entries will appear here when there is a version worth preserving as part of the product’s release history.
Newest first
Current releases stay at the top so you do not have to dig through product archaeology to find the version you are looking for.
Version and date
Every public entry gets a version number and release date so support, documentation, bug reports, and later summaries have something concrete to point to.
Summarized separately
Meaningful changes from this history are periodically gathered into Longtail Forge Updates, where related work can be grouped together and explained in normal human language.
No public release entries yet. The structure is ready when the first release entry belongs here.