Is there a reason not to use the Yahoo championed approach of embedding a version number in all static file names so you can set a very long cache expires time and just add new versions to the CDN when a change is made?
I don't know how often our CSS, branding images, scripts, and other static content change, but there would not be much effort in adding that to a deploy process and there must be developer overhead being incurred in trying to keep new code backwards compatible.
Luke Welling
On Wed, Nov 28, 2012 at 5:52 PM, Platonides Platonides@gmail.com wrote:
Code was updated to use <h3> while the (cached) skin CSS still had <h5>
See
http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2012-November/0000...
Note: code was reverted to wmf4, so the problem will appear now in the reverse.
We should use an intermediate CSS with rules appliying to portlets no matter if they are h3 or h5. Then migrate again in a few days.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l