Change Details

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 what stability they should have now. [] Create and deploy a RESTBase change updating endpoint stability designations as agreed based on the above chart

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 what stability they should have now. [] Create and deploy a RESTBase change updating endpoint stability designations as agreed based on the above chart

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 what stability they should have now. [] Create and deploy a RESTBase change updating endpoint stability designations as agreed based on the above chart