Responsibilities
The WMF Release Engineering Team's mission is to enable confident code deployment with feedback loops to inform optimal delivery to production.
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team
Our Workboards
Milestones
- Release-Engineering-Team (Priority Backlog 📥) – Projects/tasks that we plan to work on, but are not in the current sprint
- Release-Engineering-Team (Seen) – Projects/tasks that we have seen, but have no current priority
- Release-Engineering-Team (Yak Shaving 🐃🪒) – Projects that are small, not goal aligned, and will take about a day
- Release-Engineering-Team (Radar) – Not currently actionable by the team
- Release-Engineering-Team (Deployment Training Requests) – Requests for training for deployments
- Unstewarded-production-error – Unstewarded code causing production errors (mainly used for tracking in traige)
Milestones with emojis
🧟 – An ended sprint with remaining tasks
🔥 – Current active sprint
Software/tooling projects
Here are the projects and components we care about:
- Release Pipeline
- Train Deployments
- Scap
- Quibble
- Deployments
- Developer Productivity
- Continuous-Integration-Infrastructure
- Continuous-Integration-Config
- Zuul
- Phabricator
- Phatality
- logspam-watch
- dev-images
- Wikimedia-GitHub
- Gerrit
- GerritBot
- GitLab
- Tool-gitlab-account-approval
- Tool-extloc
- VPS-project-devtools
- Catalyst
Our ACL (Access Control List) project: acl*releng
Team Skill Matrix
Looking for someone to help you on a specific thing? Have a look at the Release Engineering skill matrix.
Deployments
Release-Engineering-Team is responsible for the weekly MediaWiki "Train Deployments," scheduling of code deployments, deployment tooling, etc. Some helpful links below:
- Deployment Schedule
- Mediawiki Train Deployment Blockers - includes past releases
- Open Deployment Blockers - for current and future releases only
Team image: CC-By-SA-4.0 Diego Delso