[wp-trac] [WordPress Trac] #27882: Address some issues found running Scrutinizer

WordPress Trac noreply at wordpress.org
Wed Apr 23 19:12:00 UTC 2014


#27882: Address some issues found running Scrutinizer
----------------------------+-----------------------------
 Reporter:  wonderboymusic  |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Future Release
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  close           |     Focuses:
----------------------------+-----------------------------
Changes (by bpetty):

 * keywords:   => close


Comment:

 Marko is right, I've also been tracking Scrutinizer recently too, but
 until we have specific fixes in mind (and ideally patches to go with
 them), it's pointless to open a general "placeholder" ticket that can
 never be discussed (because it's not about specific issues), resolved, and
 closed. There will always be new Scrutinizer issues, and very likely
 several that will never be fixed for numerous reasons mostly related to
 back-compat.

 FWIW, here's my public Scrutinizer report since none was even linked yet:
 https://scrutinizer-ci.com/g/tierra/wordpress/issues/master

 Please note that Scrutinizer has *not* been configured for known WP-
 specific rulesets, so much of these reports are going to be incorrect or
 not applicable, especially for 3rd party libs.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27882#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list