Last modified: 2013-08-31 22:33:30 UTC
After brion's bug 27147 comment 3; Either server side or client side. JS: The links would be given a class around: http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/bugzilla/bugzilla-4.0/extensions/Wikimedia/Extension.pm?revision=84488&view=markup#l66 and a call to the mw.org api would get the status. Serverside: A way to query the database or api from there serverwise and put it directly in the output. See also * (bug 27147) Reflect current revision status in links within CR work flow
Revision status can be fetched from CodeReview via API: http://www.mediawiki.org/w/api.php?action=query&list=coderevisions&crrepo=MediaWiki&crrevs=12345&crprop=revid|author|status|timestamp&format=json { "query": { "coderevisions": [ { "revid": 12345, "status": "old", "author": "nikerabbit", "timestamp": "2006-01-02T01:00:38Z" } ] } } Note this is also something that could be done from client-side JS so the lookups don't delay page generation. Emit an appropriate class for the rev links, and JS can go look them up in a batch.
Bugmeister is the new Bugzilla maintainer and default assignee.
Resetting to default per bug 37789
In times of Gerrit (we abandoned CR which this request is about) we have the Gerrit Notification Bot in Bugzilla which announces 1) related patches made available for review, and 2) related patches having been merged by adding a comment to the related Bugzilla ticket. This sounds sufficient to close this as RESOLVED WORKSFORME, but please reopen if you disagree.
