Dev Chat Summary: November 16 (4.7 week 13)

This post summarizes the dev chat meeting from November 16th (agendaSlack archive).


  • Dev Chat timing: Weekly chat has been moved to 21:00 UTC.
  • Schedule: Thursday, November 17th is the target for RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).! RC means the list of tickets should be at zero (with the exception of the about page), as a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). is supposed to represent software you believe you can release. It is currently at 24.
  • Tickets:For any tickets you’ve moved into the milestone, please get these resolved in the next day.
  • Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.: These should all be published this week, with a collective Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. forthcoming from @jorbin.

Dev Notes / Field Guide for 4.7

  • There are a few outstanding Dev Notes, but it’s getting close. We’re waiting on the Customize summary from @celloexpressions, Media summary from @joemcgill, Starter Content from @helen, and @davidakennedy is finishing up one on Twenty Seventeen.
    • Media summary is ready to publish, was just waiting on the PDF post from Tuesday, November 15th.
    • Video Headers post could be done by @bradyvercher, but @joemcgill own making sure it happens
  • @jorbin started drafting the Field Guide, but he’s going to need to hand off finishing it off since he will be offline starting Thursday, November 17th for a week.
    • @adamsilverstein and @jbpaul17 will work to finish things up
    • @jorbin to coordinate with Adam and Jeff to sure the remaining tasks are sorted out
    • @ipstenu happy to proofread for typos and grammar.
  • @jorbin also started the discussion to ensure the email to 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 Plugin Directory or can be cost-based plugin from a third-party devs goes out after the Field Guide is published.  That’s a collaboration with the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team and the pluginsrepo team.

Release Candidate

  • @helen (thankfully) was able to move RC back from Tuesday, November 15th to Thursday, November 17th.
  • However, we’ve got 23 tickets hanging out in the report, 22 of which need to be resolved or punted in order to reach RC.
  • [Bug Scrub of remaining 4.7 tickets proceeded]

#4-7, #core, #dev-chat, #summary