What we record
We use release notes to describe changes that matter to visitors: page navigation, responsive layout, installation assistance, offline availability, product status, contact paths, and documentation updates. Each note explains the user-visible result instead of repeating an internal task name.
Evidence matters
We record what was actually tested. A file-integrity check, a page review, a hosting preview, and a real-device test prove different things, so we do not report them as equivalent. When a test has not been performed, we say so rather than implying a full quality review.
Compatibility and risk
When an update affects installation, offline availability, stored preferences, or page addresses, we explain what visitors may notice and whether they need to refresh or reopen the site. Cached information can temporarily differ from a fresh visit, so changes to offline behaviour need repeat-visit testing as well as first-load review.
Public change history
We keep public notes focused on outcomes, known limitations, and meaningful product changes. Internal technical details belong in restricted operational records where appropriate, not in public copy that does not help a visitor decide what to do.
Current product stages are listed in the product status guide.