mcs: Update endpoint stability information #1317
Conversation
|
TODO: Link to the announcement |
test/features/mobileapps.js
Outdated
| @@ -18,6 +18,7 @@ describe('Mobile Content Service', () => { | |||
| }) | |||
| .then((res) => { | |||
| assert.deepEqual(res.status, 200); | |||
| assert.deepEqual(res.headers.deprecation, 'Sat, 01 Jul 2023 00:00:00 GMT'); | |||
There was a problem hiding this comment.
Should this and the other be sunset instead of deprecation? I think @brightbyte was suggesting following the IETF draft in https://www.rfc-editor.org/rfc/rfc8594.html#section-3 (if deprecation is just a magical alias for sunset, please advise). No strong feeling here, just wanted to make sure I understood correctly!
There was a problem hiding this comment.
I think you are right, updating the patch.
There was a problem hiding this comment.
The Sunset header is appropriate when we have set a data for decomissioning.
There is also a draft for a Deprecation header, which can be used earlier in the life cycle: https://greenbytes.de/tech/webdav/draft-ietf-httpapi-deprecation-header-latest.html
There was a problem hiding this comment.
This is the spec Ι confused with the one you mentioned before @brightbyte
|
I think something somewhere shoudl reference https://www.rfc-editor.org/rfc/rfc8594.html. Probably in a comment in the source code. |
Related phabricator patch: https://phabricator.wikimedia.org/T328036