Dev Chat Summary: July 27, 2016

WordPress 4.6 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)., 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 committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.. No exceptions. Guest committers can commit to unit tests at any time.

There are currently 2 tickets in These and any future tickets shouldn’t be open for longer than 24 hours.

About page

Unfortunately, the About page wasn’t able to be committed to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. prior to RC1, but @hugobaeta has been working hard to get it ready. You can see a draft here:

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:

Component announcements/updates

  • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. 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:

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