On Sat, Mar 8, 2014 at 1:38 PM, Tyler Romeo tylerromeo@gmail.com wrote:
On Fri, Mar 7, 2014 at 7:04 PM, Ryan Lane rlane32@gmail.com wrote:
Yes! This is a _good_ thing. Developers should feel responsible for what they build. It's shouldn't be operation's job to make sure the site is stable for code changes. Things should go more in this direction, in
fact.
If you want to give me root access to the MediaWiki production cluster, then I'll start being responsible for the stability of the site.
You don't work for WMF, so you personally have no responsibility for the stability of the site. It's the WMF developers who have a responsibility to ensure code they're pushing out won't break the site. As an aside, root isn't necessary to maintain MediaWiki on WMF's cluster ;).
Tell me something, what about the developers of MariaDB? Should they be
responsible for WMF's stability? If they accidentally release a buggy version, are they expected to revert it within hours so that the WMF operations team can redeploy? Or will the operations team actually test new releases first, and refuse to update until things start working again?
You're confused about the role of operations and development, especially with respect to organizations that let developers deploy and maintain the applications they develop.
- Ryan