Last modified: 2011-04-14 17:41:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 28382 - Do static analysis on REL1_17
Do static analysis on REL1_17
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Sam Reed (reedy)
Depends on: 28421
Blocks: 26676
  Show dependency treegraph
Reported: 2011-04-02 00:06 UTC by Sam Reed (reedy)
Modified: 2011-04-14 17:41 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Sam Reed (reedy) 2011-04-02 00:06:17 UTC
bug 28378 was a mess. Starting afresh.

It seems there's a few merge artifacts, etc etc. Be nice if we can tidy them up (Platonides script seems to work wherever it see's fit...)

Stuff like r85168, r85141 rally need properly checking over
Comment 1 Sam Reed (reedy) 2011-04-02 00:35:51 UTC
Probably worth poking around with debugging and strict etc too...
Comment 2 Sam Reed (reedy) 2011-04-04 20:46:32 UTC
bug 28421 found whilst doing it

As was r85364
Comment 3 Sam Reed (reedy) 2011-04-04 20:57:02 UTC
lint.php reckons all is ok
Comment 4 Siebrand Mazeland 2011-04-13 16:35:28 UTC
This is currently logged as a 1.17 tarball blocker. Comment 3 suggests all may be OK. What exactly needs to be done to be able to mark this issue as resolved?
Comment 5 Mark A. Hershberger 2011-04-14 17:41:27 UTC
I think we were waiting on the resolution of the bug mentioned in Comment 2, which is now resolved.


Note You need to log in before you can comment on or make changes to this bug.