Versioning
This document explains the versioning policy for Schoolyear AVD, ensuring you understand how updates are delivered and what to expect with each new release.
Continuous Development
Section titled “Continuous Development”Schoolyear AVD is under active development, with new features and fixes released continuously. Many of these updates are automatically applied to all customers without requiring any action from administrators.
However, some features require changes to your Azure infrastructure. As you manage this infrastructure, these updates cannot be performed automatically.
Versioning Levels
Section titled “Versioning Levels”To clarify the impact of each update, Schoolyear AVD uses a three-tiered versioning system:
- Patch: These are backward-compatible bug fixes and minor improvements that are applied automatically. They do not require any action from the customer.
- Minor: These releases introduce new features or significant improvements that may require a small, non-disruptive change or action from the customer. For example, enabling a new feature flag or running a simple script.
- Major: These updates include significant new functionality or breaking changes that require a more involved and planned effort from the customer to adopt. This could involve infrastructure changes or data migration.
Update Cadence and Deprecation
Section titled “Update Cadence and Deprecation”New versions are released as they become available and do not follow a fixed schedule. This allows you to decide when to update and to which version, providing flexibility to fit the updates into your own schedule.
The only constraint is the deprecation deadline for each version. After a version is deprecated, it will no longer receive support or security patches. The deprecation policy is as follows:
- Minor versions: The previous minor version is deprecated 6 months after a new one is released.
- Major versions: The previous major version is deprecated 12 months after a new one is released.
Security Updates
Section titled “Security Updates”Security is a top priority, and fixes are released as quickly as possible. Depending on the nature of the fix, it will be delivered in one of two ways:
- Automatic Patches: If a security fix can be applied without requiring manual intervention, it will be automatically rolled out to all supported versions.
- Manual Patches: If a security fix requires a manual update, a new minor version will be released for all supported major versions. You will then need to update to this new minor version to apply the security fix.