Proposal to re-designate the forthcoming 0.9 release as 1.0

[paulhowardarm]

In the weekly community meeting of 12th January 2022, it was proposed that the next release of the Parsec Service should be designated and tagged 1.0 rather than 0.9.

The rationale for this proposed change is that it better reflects the state of the project in terms of its readiness for greater adoption. The past year has seen a significant investment in maturity of the code base and the processes surrounding it: we have defined rules for API stability and backwards-compatibility, and invested in our CI process to enforce them. There are currently no further outstanding items in our backlog that are aimed specifically at this goal. A 1.0 release tag indicates that we have a stable baseline contract between the service and its clients, onto which we can build new features and capabilities.