[wp-trac] [WordPress Trac] #44600: Update WPCS to 1.0.0, and enforce coding standards

[WordPress Trac]

#44600: Update WPCS to 1.0.0, and enforce coding standards
------------------------------+-------------------------------
 Reporter:  pento             |       Owner:  pento
     Type:  task (blessed)    |      Status:  assigned
 Priority:  normal            |   Milestone:  5.0
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  coding-standards
------------------------------+-------------------------------

Comment (by jrf):

 > Solely for reproducibility. I'm not concerned about new sniffs, but if a
 sniff bugfix changed the behaviour, it would cause problems for anything
 relying on that behaviour to not change.

 > For consistency. Whilst building Gutenberg, we've found it to be far
 safer to use exact version numbers for all packages, as behaviour can
 unexpectedly change, even in bugfix releases. Rather than choose packages
 that can be safely allowed to use the latest version, it's better to fix
 all version numbers, and upgrade as we need.

 That's what the `composer.lock` file is for.... or am I missing something
 ?

 > Can WPCS releases move a bit faster than they have previously?

 Now 1.0.0 has been released, it is my intention to release more regularly,
 especially when there are notable changes. What with WPCS using semantic
 versioning, releasing new versions should be easier now as the versioning
 communicates the impact of the release.

 > Sure, it should probably throw there, too.

 Would you mind opening an issue in WPCS for this ? This is a significant
 change, so I'd like to see some responses from the community before making
 it, though I personally fully support this change.

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