Dev Chat Summary: August 3, 2016

Current status of WordPress 4.6

  • The 4.6 branch was created this week.
  • RC2 was scheduled for today, but because https://core.trac.wordpress.org/report/6 has so many open tickets its being delayed by 24 hours.
  • The first draft of the About page was committed today. Please help review it to make it ✨ Shiny ✨
  • @hugobaeta is looking for feedback on the images he’s created for the About page. The feedback will be heard and discussed in the #design weekly chat on August 4th, 2016 at 20:00 UTC.

Schedule for the next 13 days

The schedule is as follows:

  • August 10 is RC3 with the hard string freeze. The about page must be finalized by then.
  • August 12 will be code freeze. Everything should be done by this date. Only version bumps and the video should committed after this.
  • August 15 is the dry run for WordPress 4.6. We’ll check everything, prepare w.org, do a dry run for release day, and with @davidakennedy and @karmatosed we’ll release the new versions of our default themes as well.
  • And well, August 16, 2016. WordPress 4.6!

About page

As already mentioned, a first pass is committed. Check your dashboard and let us know what you think. Maybe ask some friends who aren’t involved in the release since that’s our target group.

Call for volunteers

The call for future release leads has been published. Leading a release can be a rewarding challenge. If you have questions, feel free to ping @jorbin or @helen. Everyone interested, please express it on the post, pinging @jorbin or @helen isn’t enough. They are more so available for answering questions. https://make.wordpress.org/core/2016/08/01/release-leads-call-for-volunteers/

Component announcements/updates and Open discussion

Currently the contributor handbook is lacking in documentation in regards to contributing via git. Core has supported git contributions for over 2 years. If you have a git work flow, use git, or have git knowledge in general, please consider looking over https://make.wordpress.org/core/handbook/contribute/ and adding docs where appropriate. Please remember that supporting git does not mean using GitHub.

Find full chat logs here: https://wordpress.slack.com/archives/core/p1470254406001902

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

Dev Chat Summary: July 27, 2016

WordPress 4.6 Release Candidate, announcements and our next steps

WordPress 4.6 Release Candidate 1 was made available for testing today. If you have any plugins or themes, please starting testing them against WordPress 4.6.

As always, Release Candidate availability also means there is a string freeze in place and all commits must be reviewed by two or more permanent committers and made by a permanent committer. No exceptions. Guest committers can commit to unit tests at any time.

There are currently 2 tickets in https://core.trac.wordpress.org/report/6. These and any future tickets shouldn’t be open for longer than 24 hours.

https://wordpress.org/news/2016/07/wordpress-4-6-release-candidate/

About page

Unfortunately, the About page wasn’t able to be committed to trunk prior to RC1, but @hugobaeta has been working hard to get it ready. You can see a draft here: https://cloudup.com/cDgw_UvCluc

WordPress 4.6 still needs a tagline. What should a tagline cover?

  • What do you think people will be the most excited about?
  • What would actually make you keep reading an about page and possibly feel excited to go try something out?

Much discussion happened during the meeting. You can read the conversation and suggested tag lines starting here: https://wordpress.slack.com/archives/core/p1469651308001266

Component announcements/updates

  • Trac issues are hopefully fixed.
  • To improve the review workflow during RC @ocean90 is looking into a fix which currently prevents us from branching earlier.

Open discussion

#29204 was brought up, but its unfortunately to late to be resolved in the 4.6 release cycle.

 

Full meeting logs can be found here: https://wordpress.slack.com/archives/core/p1469649667001211

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

Dev Chat Summary: July 20, 2016

WordPress 4.6 Beta 4 and current progress

Beta 4, the last beta before RC1, was released today. Please test and report all bugs you encounter on Trac.
There are still 9 open tickets that should be closed by RC1 next week. https://core.trac.wordpress.org/report/5

Dev notes, field guide, email to plugin authors, 4.6 OMGWTFBBQ Draft Post

  • @jorbin started outlining/drafting the field guide and will have a first draft in the next 24 hours for committers to review.
  • The email to plugin authors will be sent in conjunction with the release of RC1.
  • The 4.6 OMGWTFBBQ Draft Post is a post by the support team. You can find it here: https://make.wordpress.org/support/2016/07/4-6-omgwtfbbq-draft-post/. The support team especially appreciate suggestions for the “Not a Bug” section (these are items which are intentional changes, but may seem like a bug or glitch to users offhand, like Dashboard fonts being different).

About page

Feature Pointers

There are no feature pointers planned for 4.6. If your feature is planning on using a feature pointers, please consider if you really need to.

Let’s find a tagline.

The brainstorming document can be found here. There are a few suggestions for a tagline already, but please add them to the doc. Please keep it serious.

Project updates

register_meta()

@jeremyfelt published an updated dev note for the recent change (https://make.wordpress.org/core/2016/07/20/additional-register_meta-changes-in-4-6/). It was shipped with beta 4 and also announced in the release post.

Font Natively

There are currently some alignment issues related to line-height. These will continue to be worked on as needed. Please report any other issues you may run into.

Component announcements/updates

None.

Open discussion

None.

 

You can read the full chat logs here: https://wordpress.slack.com/archives/core/p1469044867000364

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

Dev Chat Summary: July 13th, 2016

WordPress 4.6 Beta 3 and the future.

  • Beta 3 was released today. Please test and report bugs on Trac.
  • There will be one more beta and some RCs, each released at 18:00 UTC like beta 3 was.

Dev notes

  • Thanks to everyone who published their notes or are still working on them. All but two (one for the HTTP API and one for the editor ) have been completed and published.
  • 15 dev notes have already been published for this release.
  • The published posts can be found here: https://make.wordpress.org/core/tag/4-6+dev-notes/
  • Posts that need to be written can be found here: https://wordpress.slack.com/archives/core/p1467832210003199
  • The goal is to have the remaining two published by Monday.

Ticket milestones

The goal for beta 3 was 40 tickets, and at the time of release there were currently 36 open tickets on the milestone.

For the remaining releases, the number of open tickets should be as follows:

  • Beta 4: 10 tickets
  • RC1: 0 tickets

The tickets left on the milestone can be found here: https://core.trac.wordpress.org/query?status=!closed&milestone=4.6&groupdesc=1&group=type&order=priority

About page

  • #37246 is the corresponding ticket and the brainstorming document can be found here.
  • The first draft of content, written by @jorbin, has been completed. Please take a look at the document and leave some feedback.
  • Everyone is invited to help with the about page.

Feature project updates

Register Meta

Font Natively

  • GitHub has recently switched over to using system fonts as well.
  • There is an open issue with bubbles and tabs (see this comment) that needs to be resolved.
  • There is patch for the tabs: https://core.trac.wordpress.org/attachment/ticket/36753/36753.6.patch. If you have time, please test it with different fonts, and report back on the ticket with results.
  • @helen mentioned there are outstanding issues with perceived smaller font size, Ubuntu font suitability, and minor alignment details.

Shiny Updates

  • There is only one remaining ticket (#37233) which needs some testing.

Component announcements/updates and Open discussion

  • @ocean90 (the 4.6 release lead) reminded developers to assign good-first-bug tickets to patch contributors to ensure they’re marked as “claimed” in the Good First Bugs report.
  • @ocean90 also reminded component maintainer who cannot add the commit keyword or change the milestone of a ticket, to ping him to fix that.
  • @ocean90 also asked for help with two tickets for PHP 7.1 compatibility, #37295 and #36435.
  • In the Media component, @joemcgill asked for additional testing assistance with #34384 to try to uncover any edge cases that aren’t covered if possible. If none are found, the plan is to commit the latest patch (or similar) later this week.
  • Additionally in the Media component, @joemcgill asked for anyone with more experience with the internals of wpMediaElement,  to help with #36735.
  • @boonebgorges is planning a minor update to wordpress-importer in the next week or two, specifically for supporting termmeta #37213 and may also fix a couple of minor issues with PHP errors, deprecated function calls, etc. Help putting together or testing the minor update is welcome.
  • There was brief discussion on the plugin/theme update preview sandbox feature suggestion (#37301).
    • @jorbin pointed out that there’s an issue with plugins that do database updates during upgrade routines between versions, and it isn’t clear how the feature would deal with that.
    • It was proposed that a second copy of the database tables would be used for the sandbox feature (using a separate prefix as the main tables), with the downside of doubling the size of the database.

The full meeting logs can be found here: https://wordpress.slack.com/archives/core/p1468440017003941

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

Dev Chat Summary: July 6th, 2016

WordPress 4.6 Beta 1 and 2 and the future.

  • Beta 2 was released today. Please test and report bugs on Trac.
  • There will be two more betas and some RCs, each released at 18:00 UTC like beta 2 was.

Dev notes

  • Thanks to everyone who published their note today or is still working on it.
  • The published posts can be found here: https://make.wordpress.org/core/tag/4-6+dev-notes/
  • Posts that need to be written can be found here: https://wordpress.slack.com/archives/core/p1467832210003199

Ticket milestones

For the remaining releases, the number of open tickets should be as follows:

  • Beta 3: 40 tickets
  • Beta 4: 10 tickets
  • RC1: 0 tickets

About page

  • #37246 is the corresponding ticket and the brainstorming document can be found here.
  • @hugobaeta and @karmatosed volunteered to help with design.
  • @jorbin will come up with a rough draft for the content of the page.
  • @joemcgill volunteered to help get responsive images into the page.

Feature project updates

Font Natively

There is currently an issue with the Windows system font. It displays smaller than previously. @helen and @jorbin are working on the best path forward. If further action is needed and you are a Windows user, please help test any patches/commits related to font sizing.

Shiny Updates

  • There are 4 open tickets regard Shiny Updates.
  • There are some issues with the Shiny Plugin Search feature and some discussion and a patch has been produced, but the design team needs to weigh in as there could be some UX/UI changes needed.
  • The dev-note for Shiny Updates will be published shortly after dev chat.
  • Shiny Updates V3 has kicked off, with the main focus being on update-core.php.

Component announcements/updates and Open discussion

@spacedmonkey brought up #37189, but it is considered an enhancement and the enhancement window has closed for 4.6.

The full meeting logs can be found here: https://wordpress.slack.com/archives/core/p1467835204003205

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

Dev Chat Notes: June 29, 2016

Feature Freeze and WordPress 4.6 Beta 1

As of today, trunk is closed to all new features and enhancements for the 4.6 release cycle.

During the meeting, attendees talked over the 4 remaining tickets and got them committed/punted/closed as needed.

Dev notes

Currently, only one dev note has been written. If you helped contribute to a significant feature or bugfix (or if you are great at writing articles), please write a dev note. If you don’t have the proper permissions on Make/Core, please work with someone who does.

You can find a list of improvements that need dev notes here.
You can find a guide to writing posts here: https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/

Feature project updates

Font Natively

The only remaining items is that a dev-note needs to be written and a coding standards commit needs to take place before release.

Shiny Updates

There are a few remaining tickets that need to be fixed during the next couple weeks.

Component announcements/updates & Open discussion

The XML-RPC endpoint on Trac now accepts attachments from all users, which means grunt upload_patch:XXX where XXX is a ticket number should work for everyone. Props @jorbin, @nacin.

 

The full chat logs can be found here: https://wordpress.slack.com/archives/core/p1467230418002461

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

Dev Chat Summary: June 15th 2016

This post summarizes the weekly dev meeting on June 15th, 2016.

Update on WordPress 4.5.3

Still targeting Tuesday, June 21st 2016 at 14:00 UTC.

Feature project updates

Font Natively

@helen updated the system fonts ticket with screenshots of the test page. The ticket still needs a few more screenshots and a patch for font-weight.

Directly after the meeting @coderste submitted a patch for the remaining font-weight issues.

Shiny Updates

The results of Monday’s Shiny Updates meeting gave a partial merge approval. The commit was made today [37714]. Congratulations to the Shiny Updates team and all who were involved in any way. @swissspidy is going to lead the project for the rest of the cycle.

Dev notes and initial field guide planning

The Field Guide is an effort that the Core Team make each release to inform developers about important changes in the release. The Field Guide is made up of links to individual posts known as dev notes. Dev notes include things like new features, changes to watch for, and potential areas for breakage. As an example, here is the Field Guide for 4.5: https://make.wordpress.org/core/2016/03/30/wordpress-4-5-field-guide/

Please note: dev notes do NOT need to be written by committers. Someone can work with first time authors to help them feel comfortable writing a post. If you would like to contribute to the 4.6 Field Guide please speak up in the #core Slack channel and someone will help you on your way.

Topics that need dev notes and their potential authors:

WCEU Contributor Day

For the #core group there are currently ~140 signups. 20%-40% of these signups are new or not an experienced contributor (yet 🙂). Contributor days are meant to change that.

Review handbook pages and good-first-bug report

In order to effectively help those seeking to begin contributing to WordPress, both the contributor handbook pages and the good-first-bug report need to be reviewed and refined. These help guide new contributors in finding something to work on and properly submitting a patch.

@lukecavanagh showed interest in helping with reviewing the handbook pages.

Workshop about preparing a dev environment for core

The core group is going to be huge and it will be way more productive for everyone if there was someone experienced to help new people set up their dev environments. The WCEU team is looking for someone (with a backup) to lead a workshop about preparing a dev environment for core. @adamsilverstein volunteered to help with the workshop. @jeremyfelt is going to help if any issues come up with VVV.

If anyone else is interested please contact @_dorsvenabili or @petya.

Component announcements/updates

None.

Open discussion

  • #12706 needs some eyes and an architectural decision before it can move forward. It may be a good candidate for a feature project.
  • In 4.5, the login <title> structure was fixed, but the admin pages were missed. #35774 aims to fix that.
  • #34923 is seeking feedback for accessibility, design, code review, docs, and general comments.

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

Dev Chat Summary: June 8th, 2016

Update on WordPress 4.5.3

Target date/time is Tuesday, June 21st 2016 at 14:00 UTC.

Consider the Shiny Updates plugin 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 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 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.

Font Natively

  • The font weight issue is still outstanding. If you can volunteer, please see: https://core.trac.wordpress.org/ticket/34923#comment:41
  • The ticket still needs screenshots of admin pages. See the above link.

Toolbar Experiments

  • No updates.

Component announcements/updates

  • 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 scrub this Friday, June 10th 2016 at 11:00 MDT. All enhancements without a working patch will be considered punt 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 🙂

Open discussion

Nothing.

 

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

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

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.

Beta 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 bug 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 core patch will be prepared by next dev chat.

Customizer 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 UX problem where 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 plugin should have a 0.6.0 release on 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 taxonomy 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 API 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 github 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

Dev Chat Summary: May 25th, 2016

This post summarizes the weekly dev chat held on May 25, 2016 at 14:00 MDT.

Update on WordPress 4.5.3

  • Work continues on the 8 remaining tickets tagged for the release: https://core.trac.wordpress.org/tickets/minor; most tickets are either fixed or marked as commit.
  • #36861 needs some testing. Please give the latest patch a try and report your findings on the ticket.
  • Since @mike reached out to hosts and got Imagick issues fixed, #36534 is no longer critical.
  • Release is still scheduled in 1-2 weeks.

Autoloading in Core

  • The discussion was about #36335 and #36926 which should be read by everyone.
  • @azaozz raised the question “How much easier would be to do this at the same time as dropping support for PHP 5.2? Or rather, would it be a good enough reason to drop that support?” since PHP 5.3+ would make the compatibility shim for spl_autoload_register() superfluous.
  • @ocean90 mentioned it wouldn’t be easier and it’s not a good idea to combine both topics because one is not a requirement for the other.
  • No further objections for the compatibility shim were raised, #36926 was approved for commit.
  • The discussion about the implementation of an autoloader didn’t come to a result because of lack of interest.

Feature project updates

Shiny Updates

  • Testing instructions were added to the feature project landing page and plugin readies.
  • The team got lots of feedback and fixed many bugs.
  • Merged activation flow for plugins that were just installed.
  • Added more QUnit tests.
  • Still targeting 4.6 with no current blockers.
  • Some bugs still need fixing and user tests for update-core.php and themes.
  • A merge proposal and core patch also need to be worked up.
  • If you haven’t already, please test the plugin: https://wordpress.org/plugins/shiny-updates/

Font Natively

  • Edge is addressing a bug and the fix will be in Edge in the next few months.
  • If you want to help with fixing font weights, please see #36753.

Customizer transactions/Customize Posts

  • For transactions, the commit has been made for adding a setting validation model (#34893). Big thanks to #design team for their input.
  • For Customize posts (#34923), a working patch has been added which connects the available nav menu items UI with being able to create new posts/pages.
  • A GIF demo that @celloexpressions prepared for the scope of the feature being proposed for core: https://core.trac.wordpress.org/raw-attachment/ticket/34923/34923.ui.1.gif
  • Adding new pages via available nav menu items is still targeted for 4.6.
  • Setting validation is already in trunk.
  • The rest of transactions will be in a future release.
  • #36944 has been opened for to give early feedback when setting validation fails, allowing server-sent validation errors to be received prior to hitting save. A key UX improvement.
  • Adding a term in the Customizer is currently impossible because there is no draft status for terms.
  • TODO: continue iterating on adding posts via Customizer, explore adding terms via Customizer, and improve setting validation.

Fields API

  • There are continued efforts to improve register_meta() in #35658 so it can support additional arguments needed by both Fields API and the REST API projects.
  • The REST API team is on board with the code thus far, but a decision needs to be made on whether or not they want to enforce a data_type or schema argument this early on.
  • Next steps are to add unit tests for new use cases and to ensure backwards compatibility.
  • #35658 is targeted for 4.6.
  • The project itself is no longer treated as a feature project for 4.6.

Toolbar Experiments

  • Notes from last weeks meeting surrounding strategy and design for a new Admin API can be found here: https://make.wordpress.org/core/2016/05/23/may-20-toolbar-and-admin-menu-meeting-summary/
  • Still targeting for inclusion in 4.6 with no blockers currently.
  • Next meeting is on Friday, May 27th at 16:00 UTC.

Component announcements/updates

  • https://make.wordpress.org/core/components/ includes a colum for “Tickets with 0 replies”. These tickets would be great to go through during a bug scrub.

Open discussion

ID or id in object properties?

Core currently has no standard on using $object->ID vs. $object->id. WP_User currently has a magic getter for id and throws a _doing_it_wrong. Its been proposed that everything use id and have a magic getter for ID that throws a _doing_it_wrong. This would involve reversing current behavior in WP_User. This would also increase consistency in core going forward. @jeremyfelt will open a ticket for standardization (#36946).

Tickets

  • #26511 is still waiting for feedback.
  • @ronaldhuereca will prepare a patch for #36872.
  • #12922 still needs discussion on whether or not posts should automatically be updated when a featured image is added. It seems that most people lean towards requiring an update before the featured image is saved.

 

The full dev chat logs can be found here: https://wordpress.slack.com/archives/core/p1464206418006799

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