Wikimedia Release Engineering Team: Difference between revisions
Content deleted Content added
No edit summary |
Tens of use Tags: Reverted Mobile edit Mobile web edit |
||
Line 153: | Line 153: | ||
==See also== |
==See also== |
||
* [[mail:releng|Team mailing list]] (private, subscription moderated, internal business only) |
* [[mail:releng|Team mailing list]] (private, subscription moderated, internal business only) |
||
== Subpages == |
|||
<div class="toccolours mw-collapsible mw-collapsed" style="overflow: hidden; /* make sure Expand button doesn't fall outside the element*/"> |
|||
{{Special:PrefixIndex/Wikimedia Release Engineering Team/|stripprefix=1|hideredirects=1}} |
|||
</div> |
|||
[[Category:Release Engineering Team{{#translation:}}| ]] |
Revision as of 22:06, 13 May 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)