Release Compatibility Documentation

[wing-utm-sharing-airspace]

Feature Request
Is it possible going forward to document in the release notes of each new candidate what the earliest backwards compatible previous release candidate is?

Backwards compatible here meaning that two DSS deployments in the same pool could be running these different releases without impacting performance or safety critical functions of the DSS.

If there is general guidance (e.g. all minor version updates within the same major version are compatible, versions are compatible if there is no schema change...) that would also help

Additional context
For context, we are not planning to run different DSS versions within the same pool for an extended period of time but this would help DSS hosts come up with a thoughtful rollout plan and cutover period when upgrading to new software releases without affecting production flights.

[the-glu]

Adding that information in the release notes (and/or documentation) seems a good idea indeed.

For the current situation / release until it's done, should that help:

I didn't explicitly tested combinations (I will do in the PR with details), but recent releases (at least 0.23.0-rc2 -> 0.20.0) should be compatible with others recent releases. Schema updates only include new functionalities / improvements and are backward compatible with old version of the code. In general, the expected procedure is: upgrade the schema and rollout restart the DSS with new images.