WordPress 7.0 "Armstrong" shipped; 7.1 alpha in development

Start of the meeting in Slack, facilitated by @audrasjb See the agenda post.

Announcements

WordPress 7.0

WordPress 7.0 “Armstrong” was released on May 20th!

Some new dev notes were published for 7.0:

WordPress 7.0.1

We have some issues in the milestone, but nothing that deserves an immediate 7.0.1 release (this the below discussion concerning potential hotfixes, though).

@jorbin proposed to publish a call for volunteers in the next couple days to target middle or end of June for the release.

WordPress 7.1

WordPress 7.1-alpha is under active development.

Two posts were published concerning 7.1:

Commence: Operation WP 7.1
WordPress 7.1 call for volunteers. @jeffpaul added that nominations will go until the end of next week, aiming to have a team finalized a week or so after that.

General

Discussion

From @masteradhoc: 3 Trac tickets/PR are waiting for review:

@audrasjb will review them in the next days.

@desrosj suggested to add a legal review to #65025 and pinged @4thhubbard to organize that.

From @jorbin:

#65286 is the ticket we are discussing. No actions are blocked, but the publishing screen on the non block editor looks extremely messy, so it’s worth cleaning it up while 7.0.1 is being worked on. @desrosj had proposed putting a fix in the Classic Editor plugin which could absolutely work. I was thinking the Hotfix plugin would make sense since it’s possible for this to affect custom post types and people may not be using the classic editor plugin at the same time. There are also other options […] but I think we should pick one and aim to get a solution out sooner rather than later.

@jeffpaul: “if we’ve not confirmed it affects CPTs, then I’m in favor of the classic editor plugin (and also that its low priority in that case)”.

@audrasjb: “I was about to say the same thing, in fact Classic Editor (plugin) seems like a really good option”.

@desrosj: “My thinking about the Classic Editor plugin instead of the Hotfix plugin is that sites that are choosing to remain using the classic editor likely have this plugin installed and activated already. So it fixes a wide number of sites just by pushing the update (provided they have auto-updates enabled, of course). I think we could still include the fix in the Hotfix plugin as well (anyone experiencing the issue without the Classic Editor plugin could install and activate), but it has far fewer users at 4,000+ compared to 9M+.”

@audrasjb: “But it wouldn’t affect websites where the Block Editor is disabled via a hook, or during CPT registration, etc.”

@davidbaumwald confirmed this affects CPTs without the Classic Editor.

@jorbin: “I like the idea of both hotfix and classic editor. I will also say that hotfix should always have a lot less users than classic editor since one is designed as a short term needed plugin and the other is the hotfix plugin”.

@masteradhoc added that the issue will be fixed on the WP Rocket plugin quite fast, as a ticket is already open there.

@jorbin and @audrasjb noted that the Hotfix plugin should be Featured in the plugins list. @audrasjb added that the plugin should also get a small assets refresh.

In conclusion, there is a path forward for the short term (use both Classic Editor and Hotfix plugins), and @jorbin and @desrosj will coordinate to put this together.

@yaniiliev asked whether there are any changes that the core team would like to see on the new profiles page? Anything missing, anything feeling off? This will be discussed during next week’s meeting. Feel free to comment this summary if you have anything to share about this topic.

#7-0, #7-0-1, #7-1, #core, #dev-chat