I made a diagram of the scap (mediawiki) deployment architecture a while back: https://commons.wikimedia.org/wiki/File:Scap-diagram.png .. That does not exactly apply to the new scap3 architecture but it's not too far off. .... On Thu, Feb 18, 2016 at 10:37 AM, Giuseppe Lavagetto <glavagetto(a)wikimedia.org> wrote: There are a lot of patches on beta these days and there have been a lot of different people cherry-picking without much coordination. This has lead to breakage quite often. Patches also get lost regularly. I assume this usually happens because someone has rebased the HEAD and accidentally dropped a patch. It can be really difficult to get a patch merged in ops/puppet within a week (or even a month). I've seen a lot of patches sit around for weeks and even now with the Puppet SWAT windows, it's still sometimes unrealistic to expect patches get merged into production that quickly. (+CC Tyler) Without a system to manage things, and with very little coordination between everyone who is working on beta, I don't expect the situation to improve too much. I intend to propose a solution for beta & puppet patch cherry-picks very soon, however, I haven't fully formulated my proposal yet. I will write to the ops list when I have something written in a clear and presentable way. _______________________________________________ Ops mailing list Ops(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops