Dev Chat Summary: November 7th (5.0 Week 6)

This post summarizes the dev chat meeting from November 7th (agenda, Slack archive). Note that the timing for this meeting will move to 2100 UTC starting Nov 14.

5.0 Planning and Updates

  • We have a lot of PRs that need review, so please pick up one or two if that’s something you excel at.
  • 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. 3 came out on Monday. Notable updates were also published about Classic Editor plugin support and meta box compatibility.
  • Patches have been issued for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 4.0 through 3.6 so that they automatically disable the 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 early enough in the 5.0 upgrade process.
  • For the upgrade process, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. will focus on messaging introducing the new editor on the post-upgrade page (aka the About page), while the Classic Editor plugin will be responsible for any communication encouraging users to give the new editor a try.
  • From the REST API desk, we are in need of some eyes/contributions on both and
  • From the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. desk, focus has shifted to generating the core JS code documentation on 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. and making it searchable. Also, the JS language packs are almost here!
  • Feature freeze on Twenty Nineteen has started, which puts all focus on these bug fixes and issues.
  • There are a number of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher related issues on the milestone for contributors who don’t feel comfortable with ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. For anyone able to test, review, or work on core PHP issues, check this report:
  • We still have a few more bug scrubs coming up this week, and could use some contributors there. A new set will be posted soon, too.

Component and Focus Updates

  • Core PHP is continuing work on Servehappy, and WSOD protection.
  • Core JavascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. meeting covered a lot of ground (Node LTS 10.13.0, back compat, e2e tests, ). Recap is available here:

Announcements and Open Floor

Next meeting

The next meeting will take place on Wednesday, November 14 21:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on the upcoming agenda post so that we can take them into account.