Release Notes

No historical releases are fabricated in this pilot. Add a release note only from an approved MSPControl release record.

Contribution structure

Each release note should include:

• Release number and publication date.
• Supported upgrade path.
• Added and changed behavior.
• Fixed defects.
• Known issues and breaking changes.
• Required administrator actions.

Full documentation versioning is intentionally disabled. Create a versioned documentation branch only when a major release changes behavior so substantially that one current guide cannot serve supported installations.