-
-
Notifications
You must be signed in to change notification settings - Fork 468
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
Releasing 0.14.0 ? #1158
Comments
Fine with me. |
FYI: I've created a preliminary changelog and will keep updating it until we are ready to release. Where this hadn't been done yet, I've updated the wiki pages with information about new (merged) sniff properties and whitelist flags. I've also created PRs #1161 and #1162 to be in sync with the release. |
I'm hoping to get clarification about a potential issue with the new |
Please let me know if I need to make any changes. :) |
Further on #1157, I would like to propose releasing WPCS 0.14.0 some time over the next two weeks.
The release as it is, is already quite feature rich: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/milestone/14
I think it would be great if we could still get #1135 and #1136 over the finish line before then.
Core
#1135 is waiting on feedback from @pentoCore
#1136 is waiting on feedback from @pento (in general) and from the @WordPress-Coding-Standards/wpcs-admins with regards to Add new Arrays.MultipleStatementAlignment sniff toCore
#1135 (comment)With #1157 in mind, I would like to propose leaving #1084 for a future release. /cc @GaryJones
As for #1041, this needs a new review and if nothing blocking comes up, it could ship with 0.14.0, otherwise this can be moved to a future release. /cc @emgk
Any objections ? If not, please leave feedback where feedback is requested. Thanks ❤️
The text was updated successfully, but these errors were encountered: