Update on WordPress 4.5.3
Target date/time is Tuesday, June 21st 2016 at 14:00 UTC.
Consider the Shiny Updates plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for merge
After much discussion and going through the feature project merge check list found here, Shiny Updates is not yet approved because:
- QUnit tests should be merged with existing tests
- a final design review needs to be done
- a security review needs to be done
The new deadline for feedback is Monday, June 13th 2016 at 12:00 UTC. Please report issues as quickly as possible so the Shiny Updates team has time to fix them before the deadline. Don’t wait until Monday and the extra meeting which will be held on Monday, June 13th 2016 at 19:00 UTC.
Feature project updates
Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. Transactions/Customizer Posts
- No updates during the chat.
- After chat: The team is no longer proposing to merge any significant framework from the customize posts plugin; however, #34923 is still targeting 4.6 for posts support (terms will be investigated further in the future). A fully functional patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. was posted late Monday and is awaiting feedback and testing. @celloexpressions is planning to spend some time addressing feedback in the next week provided there are things to address.
- The font weight issue is still outstanding. If you can volunteer, please see: https://core.trac.wordpress.org/ticket/34923#comment:41
- The ticket Created for both bug reports and feature development on the bug tracker. still needs screenshots of admin (and super admin) pages. See the above link.
- All enhancement tickets in the 4.6 milestone should have an owner. https://core.trac.wordpress.org/query?status=!closed&type=!defect+(bug)&type=!task+(blessed)&milestone=4.6&group=component&order=priority
- There will be a bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub this Friday, June 10th 2016 at 11:00 MDT. All enhancements without a working patch will be considered punt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) candidates.
- Please take some time to update the good-first-bug report. This is a report that new contributors are directed to and it would ideally have good-first-bugs when they go there 🙂
Full chat log can be found here: https://wordpress.slack.com/archives/core/p1465416005000791