Wikimedia Release Engineering Team: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
| start = 2014-07-28 |
| start = 2014-07-28 |
||
| group = [[Wikimedia Technology|Technology]] |
| group = [[Wikimedia Technology|Technology]] |
||
| team = [[User:BBearnes_(WMF)|Brennen Bearnes]], [[User: |
| team = [[User:BBearnes_(WMF)|Brennen Bearnes]], [[User:ADancy (WMF)|Ahmon Dancy]], [[User:Dzduvall|Dan Duvall]], [[User:😂|Chad Horohoe]], [[User:JHuneidi_(WMF)|Jeena Huneidi]], [[User:Hashar|Antoine Musso]], [[User:JNuche (WMF)|Jaime Nuche]] |
||
| Phabricator = Release-Engineering |
| Phabricator = Release-Engineering |
||
| updates = |
| updates = |
Revision as of 18:41, 29 June 2022
Release Engineering
Enable confident code deployment with feedback loops to inform optimal delivery to production.
|
Release Engineering's mission is to enable confident code deployment with feedback loops to inform optimal delivery to production.
Join our IRC channel: #wikimedia-releng connect
Values
Team Values | |||||
---|---|---|---|---|---|
🧑💻 Developer focus | 🎖️Integrity | 🌻 Freedom & open source | 🙌 Quality | 👥 Teamwork & Collaboration | |
|
|
|
|
|
Help!
See also: /Skill matrix and /Access list
Things We Do (that we can help you with):
|
Where we are: See also: https://time.releng.team
|
Quarterly Objectives and Planning
See /Goals
Dashboards
We maintain a list of dashboards that provide insight into the services we maintain and how our team is functioning.
See also
- Team mailing list (private, subscription moderated, internal business only)