Release notes format
What each section of an e6data release note covers, so you can scan releases efficiently.
Each release note in the Changelog follows a consistent structure. This page describes what each section means.
Sections
Release header
The release version, date, and components affected.
Release 1.2.3 - May 13, 2026
Components: Platform Components, Metadata ServiceHighlights
The 2–4 most user-visible changes in the release. Scan this first.
New features
User-facing capability additions. Each entry links to the relevant doc page.
Improvements
Performance, reliability, or usability improvements that don't add new surface area.
Bug fixes
Fixed issues. Each entry references the bug ID (for example, E6-1234) for support reference.
Breaking changes
Anything that changes existing behavior in a way that could affect customer queries, configurations, or integrations. Always read this section before upgrading.
Deprecations
Features marked for removal in a future version. Lists the deprecated feature, the recommended replacement, and the planned removal date.
Security advisories
Security-relevant fixes. Includes severity (Low / Medium / High / Critical) and whether action is required from customers.
How to use release notes
Deciding whether to upgrade
Highlights, Breaking changes, Security advisories
Looking for a specific fix
Bug fixes (search by bug ID or symptom)
Planning future work
Deprecations
Understanding new capabilities
New features, Improvements
Versioning
e6data uses semantic versioning:
Major (X.0.0)
Breaking changes possible; read release notes carefully
Minor (1.X.0)
New features; backward compatible
Patch (1.2.X)
Bug fixes and security updates; backward compatible
Major version bumps are rare (typically annually). Most releases are minor or patch.
See also
Last updated
Was this helpful?