As the Wikimedia Foundation, we have a responsibility to ensure reliability and stability of the production environment. To that end, we need to look for ways to continuously improve how we manage what code is deployed to production.
Although there are existing process is place that we already follow, there are likely improvements that could be made.
This is a parent task to track activities that are related to managing how and what things are deployed into production.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T203703 Create production code deployment management process | |||
| Duplicate | Jrbranaa | T199253 TEC13:O1.1:Q1 Goal - Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page) | |||
| Open | None | T190891 Develop canonical/single record of origin, machine readable list of all repos deployed to WMF sites | |||
| Open | None | T195244 Investigate and make improvements to the extension review process | |||
| Open | None | T203698 Add Code Stewardship review to Review Queue process | |||
| Open | None | T203701 Add Services (and other non-extensions) to the deployment review process |
Although the goal is to have all code that deploys to production go through this process, it may be necessary to have two branches in this process. One that is for "permanent" deployment to production, and one that is "conditional". For example, team needs to get new capabilities into the production environment in order to obtain timely user feedback, but the code is not fully compliant to Code Health, security, performance, etc... criteria. They may have a time-based condition to address the gaps or be removed from production.
Not sure that's the only/best approach, but I think an exception process needs to be addressed.
Another thought to capture... This process should probably result in a workflow that is as automated as possible. For example - initiated by the creation of a phab task that then auto creates other tasks from template with appropriate folks subscribed/assigned. In the end, minimizing the room for error in a manual set of steps on a wiki.