On 2012-05-04 20:16, Ross Patterson wrote:
> Elizabeth Leddy
> <elizabeth.leddy@...> writes:
>> On May 2, 2012, at 2:52 AM, Martijn Pieters
>> <mj@...> wrote:
>>> On Wed, May 2, 2012 at 7:40 AM, Nathan Van Gheem
>>> <vangheem@...> wrote:
>>>> Right, restarts should not recook registries. If your code css/js changes
>>>> either provide an upgrade step to cook or do it manually IMO.
>>> Absolutely. When I roll out updates to my largest deployment, I want
>>> the varnish and browser caches to continue to use their cached copies
>> Wow, I roll out changes several times a week and this seems
> I'm with Liz here. I get clients being bitten by this all the time when
> their CSS guys make changes and can't figure out why it's not taking
> effect. Plone has way too many such gotchas and I think have default
> behavior for large/enterprise deployments is one of the larger sources
> of such gotchas. There should be an *option* for the current behavior
> that large deployments can know about and use, but we should not be
> requiring people who want to edit CSS with Plone to write upgrade steps
> so it should not be the default.
big +1 for an option: for small sites it makes no sense to write update
steps, for big sites it makes sense. The lazy small-and-medium site way
of automatic reload after restart should be the default.
>> I'll just make an add on that checks to see if the timestamps are
>> modded on the files and cook on restart... and stay out of core. I
>> have some serious developer usability concerns on this one but my
>> keyboard is borked so enjoy the break :)
>> Thanks everyone for the feedback!
>>> Martijn Pieters
Klein & Partner KG, member of BlueDynamics Alliance