My thinking with E2 is that they want to move to train deployments (biweekly or weekly) in
any case. Though for Echo, that's not likely at the moment, so this is something to
consider when things settle down, so this is something to consider after the first Flow
extension gets released.
I believe they already do ride the train for most patches on existing projects in
On May 16, 2013, at 1:24 PM, Greg Grossmeier <greg(a)wikimedia.org> wrote:
I just want to highlight a question I have for the
various feature teams
(Staying on engineering@ so that everyone can participate, instead of
mailing individual team leads/etc.)
<quote name="Greg Grossmeier" date="2013-05-14"
== Riding the Train ==
Now is the time to start getting more development teams to start riding
the MW Core deploy train. If a one-week cycle/14 day lifespan (with the
always possible important backports available) is something doable for
your team right now, please do let me know. If it isn't, please let me
know what would be "good enough".
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Engineering mailing list