Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,075 of 9,075 pages
About the help in other languages
All help pages

Covering 6.0.15, before and after its tag

How to report on the Exponential 6.0.15 line, the current release line of Exponential 6.0 - what the sources said about it before the tag v6.0.15, how to check whether the tag exists, which phrasing is accurate, and why…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/press/covering-6-0-15-while-in-development.md

On this page

Covering 6.0.15, before and after its tag

This page is for reporters and creators who write about the work in the Exponential 6.0.15 line, the current release line of Exponential 6.0, which follows 6.0.14. Until the tag v6.0.15, the line was in development on the main branch, and coverage had to say so and give no release date, because no source gave one. Check first whether the tag exists (git tag -l 'v6.0.*' --sort=version:refname), and take a release date only from the tag.

Contents

  1. What the sources say about 6.0.15
  2. What is in the line
  3. Labeling it correctly
  4. Phrases: accurate and inaccurate
  5. When the tag arrives

What the sources say about 6.0.15

Before the tag, the sources said the following; quote them with the date they carried.

FactSource
"Not released yet. The 6.0.15 line follows v6.0.14 (2026-06-07); no tag v6.0.15 existed on 2026-10-12."6.0.15 changelog
"Date not released yet"release overview
The main branch is "the current development of the 6.0 line, today 6.0.15" and identifies itself as 6.0.15stable in lib/version.phpGetting the code
"Security fixes are made on the main branch (the 6.0.15 line, dev-main) and published with the next 6.0.x release."SECURITY.md
On 18 October 2026 the newest tag was still v6.0.14git tag -l 'v6.0.*' --sort=version:refname

Note the trap in 6.0.15stable: it is the version string of the main branch, not a release. A release is a tag (Covering a release).

What is in the line

The changelog describes "four months of work", organized by period. The highlights named in Who is 7x?, The 6.0.x releases are "Velocity, admin4, audit trail, Exponential Layouts, Exponential Intelligence, the help system and much more". The history adds the months:

PeriodWhat happened, per the historyMonth page
July 2026"The command line grew up": ezpm in the console, the Kickstarter, a password reset toolJuly 2026
August 2026Template debugging, six security patches, tests on every changeAugust 2026
September 2026Paged long lists, Velocity (from 22 September), a one-command install, a hardening sweepFirst half, second half
October 2026jQuery 4 and admin4, an audit trail, exp:ini, a debug bar, content jobs and TinyMCE 8October 2026

Exponential Intelligence and the job queue arrive in the distribution "inactive" and are switched on by the site owner (6.0.15 changelog). Mention that if you describe them.

Labeling it correctly

Put the status in the headline or the first sentence, not in a footnote. If the tag v6.0.15 does not exist on the day you check, write for example:

In development: what the next Exponential version, 6.0.15, is set to include
Exponential's development line adds an audit trail (not released yet)

In the body:

These changes are in the 6.0.15 development line of Exponential. As of <date you checked>, no 6.0.15
release had been published; the newest release is 6.0.14 of 7 June 2026. The project has not announced a
release date. Source: <link to the 6.0.15 changelog>.

Once the tag exists, call 6.0.15 a release and give the date of its tag (Covering a release).

Phrases: accurate and inaccurate

The left column was inaccurate before the tag v6.0.15; the right column is what was accurate then.

InaccurateAccurate
"Exponential 6.0.15 is out.""Exponential 6.0.15 is in development."
"6.0.15, due this autumn""6.0.15 has no announced release date."
"The new release includes ...""The development line includes ..."
"6.0.15 stable""the 6.0.15 line"
"Everyone gets Velocity in the next update.""Velocity is a separate package that Exponential's composer.json requires at ~0.0.4.57" (Getting the code)
"Feature X will be in 6.0.15 for sure.""Feature X is in the development line today"; lines can still change before a tag

After the tag, "the 6.0.15 line" is still accurate, "6.0.15 stable" is still not the product's wording, and "Exponential 6.0.15 is out" becomes accurate, with the date of the tag as the release date.

If you install the main branch for a review, say so and follow Testing the development line. Do not show a test site's addresses or sign-in data.

When the tag arrives

  1. Confirm the tag v6.0.15 (Verifying a release yourself).
  2. Read the changelog as it stands at the tag; contents may differ from what you saw before the tag.
  3. Update or correct earlier stories that described the line (Corrections and updates).
  4. Use the Release coverage checklist.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x