[Engineering] [Ops] Changes to SWAT deployment policies, effective Monday April 30th

Sat Apr 28 10:19:22 UTC 2018

On Sat, Apr 28, 2018 at 1:33 AM, Timo Tijhof <ttijhof at wikimedia.org> wrote:

> Making complex changes and refactors in mediawiki/core is fine. But if it
> can't wait for the train or can't be given its own window with full scap,
> it will need to be broken down into smaller changes that each can be safely
> merged, beta'ed, cherry-picked, verified and deployed.
>

OTOH core patches are tested way better than backports (which often have to
be forced through CI which is not all that reliable for old branches; also
backports are often not done by the developer of the code). Forcing people
to rewrite backports as multiple patches instead of just cherry-picking
might introduce more risk of error than it takes away. An alternative
approach would be to require a sync plan for config / backport patches, and
make that a requirement for +1 (and add a scap pull-file command).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/engineering/attachments/20180428/d29d14a3/attachment.html>