-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecation and retirement dates for CDR Register superseded endpoint versions needs to be defined #452
Comments
The DSB proposes the deprecation and retirement dates for the old CDR Register endpoint versions, superseded by the work in #424 and #425, should follow the conventions already established by the DSB. Currently, the alignment of the new endpoints is being assessed through #465
Retirement dates for these endpoints represent 3 months beyond the deprecation dates, plus a buffer to accommodate end-of-year industry shutdowns. |
Deprecation and retirement dates are reflected as follows:
The standards Endpoint Version Schedule contains further details This change was incorporated into release v1.17.0. Please refer to Decision 237 for further details. |
Description
With the introduction of #424 and #425, the CDR Register will release new versions of the API endpoints using endpoint versioning. Multiple versions of the endpoints will be valid for a period of time and as part of this work, old endpoint versions have not had deprecation or retirement dates defined.
This issue is being raised to determine what an appropriate deprecation and retirement schedule should look like.
Area Affected
CDR Register APIs and their associated Endpoint Version Schedule.
Change Proposed
The result of this work will be a defined deprecation and retirement date for superseded CDR Register endpoint versions
The text was updated successfully, but these errors were encountered: