I've been doing some code review today, and updated the revision report at https://secure.wikimedia.org/wikipedia/mediawiki/wiki/MediaWiki_roadmap/1.18... . The number of new revs in 1.18 dropped to 92 today, the first time it's below 100. Yay!
A side effect of reviewing code, though, is that the number of fixmes increases. We now have 64 fixme's in 1.18. The 1.18 wall of shame is:
platonides: 6 purodha, reedy, tstarling: 5 diebuche: 4 bawolff, freakolowsky, hashar, maxsem, mgrabovsky, robin, tparscal: 3 catrope, happy-melon, werdna: 2 aaron, btongminh, demon, hartman, hcatlin, ialex, mah, neilk, nimishg, preilly, wikinaut, yaron: 1
So please address your fixme's, people!
Another call to action is for reviewers who have new revisions assigned to them:
nikerabbit: 10 krinkle: 6 brion: 3 tim: 4 trevor: 2 chad: 1 neil: 1
Revision lists for assigned revs and fixme's are on the revision report.
Roan
On 08/20/2011 11:04 AM, Roan Kattouw wrote:
I've been doing some code review today, and updated the revision report at https://secure.wikimedia.org/wikipedia/mediawiki/wiki/MediaWiki_roadmap/1.18... . The number of new revs in 1.18 dropped to 92 today, the first time it's below 100. Yay!
Yay!
To make it easier to find code to review, people are tagging particular revisions with tags like "frontend" (CSS, JavaScript, jQuery) and "i18n" (localisation and internationalization).
Feel free to use those tags to find revisions to review, or -- if you don't have code reviewer status -- to "sign off" (read the code, test it, and give your opinion on whether to accept or reject it) on revisions.
Check out and add to the Code Review tagging page on MediaWiki.org: http://www.mediawiki.org/wiki/Code_review_tags
wikitech-l@lists.wikimedia.org