Steps outlined here: https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Deploy_to_Beta_Cluster
- Add the new extension submodule to the git mediawiki/extensions repo if it's not already in it. See example. This will result in the code being deployed (unused) to the Beta Cluster.
- Move your extension's CI config to the "Wikimedia production" section, add the "in-wikimedia-production" job template, and make sure it has and passes all the expected jobs for production code. (MR)
- Add your extension to the json make-wmf-branch release tool at least two weeks prior to your target date for enabling on the Beta Cluster. It will add the extension as a submodule of mediawiki/core when the weekly deploy branch is cut, and the code will be deployed (unused) to production
- Add your extension to extension-list. This requires that the code be present on every branch running in production, since extension-list is used to build the CDB database for i18n files in both Beta and production. (patch)
- Add your extension config variable to InitialiseSettings.php and set it to be default false. See example. (patch)
- Add your extension config variable (same as in previous step) to InitialiseSettings-labs.php and set it to be true on Beta Cluster wikis you want it to be on. You may want to turn it off for loginwiki (which doesn't have most extensions). (patch)
- Load your extension in CommonSettings-labs.php (patch)
We will initially enable only on kowiki for beta cluster.
Acceptance criteria:
- ReportIncident is not enabled on any production wikis
- ReportIncident is enabled on kowiki on beta cluster
- "Report" button is available on user talk pages on kowiki on beta cluster (e.g. https://ko.wikipedia.beta.wmflabs.org/wiki/%EC%82%AC%EC%9A%A9%EC%9E%90%ED%86%A0%EB%A1%A0:Bluedot?uselang=en)
