Bryan Davis <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #7 from Bryan Davis <> ---
Is this really a problem with the atomicity of the scap process in general? 

Making the MW deploy process more atomic is a goal for the "next generation
scap" project. It would be good to have some use cases such as this one
documented in the talk page for the deploy system requirements [0] or somewhere
near by so we can try and squash ugly edge case problems such as this one
related to the front end caching architecture.

One random idea that just popped into my head would be to create some system
for telling the front end varnishes that things will be changing soon and that
they should not cache any new responses until given the all clear sign.


You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to