-
-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timing of version 2.0.0 #1389
Comments
FYI: I've prepared most of the changes needed for WPCS 2.0.0. |
After some discussion, @jrfnl and I plan to do a |
FYI: I've trailed through all the PHPCS 3.x changelogs up to 3.4.0 for any other changes WPCS could benefit from and opened issues/PRs for what remained. Aside from the changelog and some minor documentation updates (and the currently open PRs), as far as I'm concerned WPCS 2.0.0 is done. Might be worth it to have a look at the older open PRs to see if any of them can go in and to trail through open issues to see if there are any which can be closed (or addressed as quick wins). |
The release candidate has been released: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/releases/tag/2.0.0-RC1 |
WPCS 2.0.0 has been released: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/releases/tag/2.0.0 |
I previously proposed to drop PHPCS 2.x support and remove all deprecated sniffs by end of August - largely with an eye on being able to have a different namespace to prevent clashes with the WP project itself.
I'd like to propose changing that deadline to end of December 2018 for the following reasons:
As there are numerous standards out there which have WPCS as a dependency, we ought to allow them some time to adjust their standard. and two (summer/vacation) months does not really sound long enough, which is why I'm proposing moving the 2.0.0 release back to the end of the year.
Opinions ?
/cc @WordPress-Coding-Standards/wpcs-admins
The text was updated successfully, but these errors were encountered: