Chad innocentkiller@gmail.com writes:
On Sun, Jan 1, 2012 at 12:49 PM, Brion Vibber bvibber@wikimedia.org wrote:
I'd like us to plan for a code freeze on trunk -- at least a feature & refactoring freeze -- starting within a few days to give us all a chance to tidy up, catch up with code review, and prepare for deployments.
+1
I'm all for it!
Sounds good. Want to say Friday's the date to be "feature complete" to give people the rest of this week?
Again, great idea.
One thing I would like to do is make sure https://www.mediawiki.org/wiki/MediaWiki_1.19 lists all user visible changes. I almost said "all significant user visible changes", but then someone might know of a user visible change, but not consider it significant and neglect to put it in there.
Starting next week, after the "feature complete" deadline that Chad has proposed, I'd like to take a list of features to the different projects and work them to try out the changes on a test deployment wiki.
I'm trying to be more proactive about this than we have been in the past, so that bugs like the now-infamous EXIF rotation problem (https://bugzilla.wikimedia.org/31504) are spotted earlier and, hopefully, dealt with *before* deployment.
I need to start doing something similar with tool upgrades, too. If I hadn't been content to simply nag Ops about deploying rsvg upgrades or recompiling wikidiff2 then bugs like "rsvg on scaler does not support styling the root element" (https://bugzilla.wikimedia.org/31122) and "Excessive punctuation highlighting in wikidiff2" (https://bugzilla.wikimedia.org/33331) might have been recognized sooner.
Mark.