Release notes — where to find them¶
Understand ships frequent builds, so per-release notes are published per build rather than hand-listed here. This page tells you where to read them and how versioning works.
Where the notes live¶
- All build notes — docs.scitools.com/buildnotes lists every build's changes (New Features, Bug Fixes, Known Issues), newest first, grouped by version.
- Major-version highlights — Version releases summarizes each version-point release (8.0, 7.2, …) and links to its full notes.
- In the product — Help → Check for Updates tells you whether a newer build is available and opens its download page; the Welcome page shows a What's New notice the first time you run a build that added features.
How versioning works¶
- Every build has a build number (for example, build 1257). Version-point releases such as 8.0 correspond to a specific build and get a highlights write-up on Version releases.
- Find the build you are running under Help → About Understand.
How the notes are generated¶
Build notes are generated per build from the project's own commit history (ninja buildnotes),
then reviewed and edited before release. Each build's notes list what changed since the previous
build, grouped into these customer-facing sections:
| Section | Contents |
|---|---|
| New Features | User-facing additions |
| Bug Fixes | Defects resolved in this build |
| Known Issues | Outstanding problems flagged for the build |
(Engineering-only notes are kept in the source but are never published.)
Upgrading?
Before moving a team to a new build, read Migrating from an older version — it
covers what happens to an existing .und project, settings, and API scripts on upgrade.