Documentation Reference Release notes
REFERENCE

Release notes

Release notes record what changes in Overseer from one release to the next. This page explains what an entry contains and how the entries are organised.

What release notes record

Each release of Overseer has one entry. The entry lists every change that affects what you see or what Overseer does on a computer, so you can tell whether a release touches the way you work before you meet the change on screen. Read them when a release arrives, and again when something behaves differently from the way you remember.

How an entry is organised

Changes in a release are sorted under three headings:

  • New. Something Overseer could not do before.
  • Improved. Something that already existed and now works better, or differently.
  • Fixed. A fault that has been corrected. Where the fault was listed under Known issues, the entry says so.

Where the list starts

Overseer is in development. The release notes begin with its first release.

Next steps

Known issuesWhat the known issues list is for and how each entry is laid out. TerminologyA glossary of the words Overseer uses, grouped by topic. API documentationWhat Overseer's HTTP API covers and how access to it is granted.
Was this article helpful?
← Terminology Known issues →

In development. Launch inquiries welcome.

This documentation describes Overseer as it is being built. If you would like to hear when it launches, get in touch.

Ask about launch