https://bugzilla.wikimedia.org/show_bug.cgi?id=51298
Greg Grossmeier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|High |Normal --- Comment #4 from Greg Grossmeier <[email protected]> --- Thanks Eduard. (In reply to comment #3) > Regarding this bug, I won't say it's a blocker: It only produces > unnecessarily > large PNGs and nullifies previous attempts of users to optimize PNGs by > cautiously reducing bit depth. It doesn't influence visual appearance, > though. Great, good to know. Reducing priority of this specific issue. > However I have general considerations regarding scaler quality (and I'd call > those blockers). I wrote a little on that in the announcement on Commons > already and I'll probably file a bug report with some test-cases this > evening. That would be great, as I don't know of those issues (I read some of the VillagePump on Sunday, but I thought everything was reported thus far). > Having that said: Is there any need for the pressure on the release date? > There > was only roughly one week between announcement and the planned deployment. > Why > not give people a little more time to test and to sort out bugs like the one > discussed here? I mean we have a working scaler in place so I assume we do > not > need to immediately deploy VIPS now? The beginning of this change started before my time, but according to the VipsScaler extension wiki page (https://www.mediawiki.org/wiki/VipsScaler) the VipsTest page on test2.wikipedia.org has been around since December 2011 (I don't know what communication was made at that time, though). The purpose of changing to Vips for a subset of image scaling jobs is to reduce memory consumption (thus be able to scale larger images). So it isn't just a needless change, but a change to improve functionality. To be clear: the scheduled deploy doesn't *have* to happen if there are blocking bugs. The only one I see now is determining the file size limit for progressive jpegs (bug 51275). See bug 51370 for tracking the config settings for VipsScaler. Please do report any other issues you have so I/we can make a fully informed decision. Thanks! -- 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 [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
