I've done release engineering before. It is my considered opinion that one person
needs to be on point for each release. It's possible that that person could rotate in
and out, but one person needs to be running through the checklist of "things that
need to be done".
________________________________________
From: wikitech-l-bounces(a)lists.wikimedia.org [wikitech-l-bounces(a)lists.wikimedia.org] on
behalf of Erik Moeller [erik(a)wikimedia.org]
Whether that would get us to a healthier balance remains to be seen,
but I think there's pretty broad agreement that adding more support to
the review/deployment/release process is a necessary precondition for
any other process changes like moving towards pre-commit review.
Clearly what's been said in this thread is true -- there are lots of
things that can be done to reduce our technical debt and make it
easier to accommodate and manage new changes, but without added
dedicated capacity, the train won't move at a speed that we're happy
with. We can't change that overnight (because we need to figure out
the right rhythm and the right processes together), but we will change
it.
Erik
--
Erik Möller
Deputy Director, Wikimedia Foundation
Support Free Knowledge:
http://wikimediafoundation.org/wiki/Donate
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l