Page MenuHomePhabricator

Audit and update MCS/PCS API endpoint stability designations
Closed, ResolvedPublic

Description

Follow-up from T248570. Many MCS/PCS endpoints are designated as unstable or (more often) experimental despite having supported stable client releases for months or years. As a courtesy to current and prospective clients, we should audit the API endpoint stability designations for MCS & PCS.

AC

  • Create a table of all current MCS/PCS API endpoints, with columns presenting their current stability designation and proposed stability.
  • Create and deploy a RESTBase change updating endpoint stability designations as agreed based on the above chart

Result

EndpointCurrent stabilityProposed stability
/page/mobile-sections[-lead, -remaining]unstabledeprecated
/page/summarystablestable
/page/definitionstablestable
/page/mobile-htmlexperimentalexperimental
/page/mobile-html-offline-resourcesnone specifiedexperimental
/page/media-listexperimentalunstable
/page/talknone specifiedexperimental
/data/css/mobileexperimentalunstable
/data/javascript/mobileexperimentalunstable
/data/i18n/mobileexperimentalexperimental
/transform/wikitext/to/mobile-htmlstablestable

Event Timeline

Mholloway renamed this task from Audit MCS/PCS API endpoint stability designations to Audit and update MCS/PCS API endpoint stability designations.May 12 2020, 3:37 PM
Pchelolo added a subscriber: Pchelolo.

PR merged and deployed. Untagging CPT, please retag if something else needed here.