Dev Chat Summary: June 1st, 2016

Update on WordPress 4.5.3

Nothing new. The last few tickets are being wrapped up so it can be shipped next week.

BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is in 4 Weeks

  • Before Beta 1, every feature should be ready to be tested.
  • Before Beta 1, every feature that needs a dev note should have one. See https://core.trac.wordpress.org/query?keywords=~needs-dev-note&milestone=4.6&group=component
  • Before Beta 1, every enhancement or feature request needs be committed or punted. See https://core.trac.wordpress.org/query?status=!closed&type=!defect+(bug)&type=!task+(blessed)&milestone=4.6&group=component&order=priority
  • Because there are so many tickets in the 4.6 milestone, next week there will be one, two, three bugbug 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. scrubs to knockout as many tickets as possible. They will be on Monday (by @chriscct7), Wednesday (by @ocean90), and Friday (by @voldemortensen). Times will be announced.

Feature Project Updates

Shiny Updates

  • Remaining issues are being fixed.
  • A merge proposal will be written by the end of this week.
  • A coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patchpatch 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. will be prepared by next dev chat.

CustomizerCustomizer 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/Customize Posts

  • For transactions: There is now an initial patch to improve setting validation to give earlier (immediate) feedback when validation errors occur, fixing a key UXUX User experience problem where invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. settings would just not appear in the preview and no indication would be provided to the user until a save was attempted. See #36944.
  • For stubbing posts/pages via available nav menu items, additional feedback on UI/UX, accessibility, and on integration with terms: https://core.trac.wordpress.org/ticket/34923#comment:41
  • The Customize Posts pluginPlugin 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 should have a 0.6.0 release on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ today which should make it much easier to test with the patch. No new iterations on the patch itself were made this week, other than framework improvements on Customize Posts.
  • No blockers
  • The current patch still has some bugs and needs to be refreshed.
  • User tests are also needed.
  • There could also be some discovery work on adding a private shadow taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. for drafted terms.
  • Unfortunately, there is still too much to be done to make it in the 4.6 release.

Font Natively

  • Still no movement and no blockers.
  • If you can volunteer to go through font-weights in Core, please do so. See https://core.trac.wordpress.org/ticket/36753#comment:32

Toolbar Experiments

  • Still targeting 4.6
  • Documentation and APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. planning is still underway.
  • More eyes on the documentation would be most beneficial. See https://docs.google.com/document/d/1oMSn_GBoly19tY2a6GfNJp8XnAvUbrGTnl2oeXdkgeg/edit

Component Announcements/Updates

Reminder: https://make.wordpress.org/core/components/ has a “0 Replies” column. If it doesn’t show “0” for a component, it needs to be fixed.

Build/Test Tools

  • A new version of grunt-patch-wordpress is coming right after this meeting that adds:
    • 1) the ability to use githubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ urls for patchs
    • 2) the ability to upload patches directly from the command line for all users with the appropriate ability in xml-rpc.
  • Its currently limited to profiles that are bug gardeners, but will soon be all users.

Editor

  • Reminder: Every week the editor team has a chat and bug scrub 2 hours before dev chat. Everyone is welcome (and encouraged) to attend and participate.

Open Discussion

Crickets.

 

Full chat log can be found here: https://wordpress.slack.com/archives/core/p1464811247007850

#4-6, #dev-chat, #summary