Anyone care to help set the date for actually doing this, so we can announce it?
See the other blockers of T96858 for code changes that are needed for a WMF deployment, and the "action=query&!rawcontinue&!continue" entries in api-feature-usage.log could give insight as to just how much might get broken.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Anomie | T96858 Use "new" continuation by default | |||
| Resolved | Anomie | T99545 Set a date for breaking API continuation |
June 3rd after branch cut? Gives people more than a week after Lyon to fix stuff, and it'll sit a week on the beta cluster for testing.
Date is to aim for deployment with the train the week of June 30, which if I count correctly will be 1.26wmf12.