November 22nd Support Team Meeting Summary

General announcements

We’ll be putting a post for the 5.0 Master List to be prepared on make/support some time this week.
It will for the most part be much the same format as previous releases, but with a heavier focus on checking for 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. errors and conflicts due to the nature of the new editors dependence on it.

In other news, we will be holding another support volunteer orientation during the WCUS contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus. Like previous iterations it will be pushed through slackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at, as link sharing and similar is easier that way. A make/support post will be filed for this as well, and non-attendees are also welcome to take part.

Checking in with international liaisons

Participants from Serbia, Russia, Sweden and Germany took part in this weeks slightly quiet chat (holidays!)

Open floor

We had some discussions about ways to encourage users to provide more initial information when creating support requests, and will be looking into improving the “yellow box of steps” that precedes the post boxes on the forums.

A quick summary on the WordPress 5.0 progression was also provided, as we’ve passed the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. deadline, we are not currently looking at a November 27th release. More details to follow as the release leadRelease Lead The community member ultimately responsible for the Release. team publish it on make/core.

And finally, a reminder that it’s OK to not know everything, feel free to skip questions that you’re uncomfortable with/don’t feel like you know enough about. If you’re not happy answering a question, you are in no way required to take it on!

Read the meeting transcript in the Slack archives. (A Slack account is required)