WordPress 6.5 shipped on 2 April 2024. I was one of its two Editor Tech Leads, alongside Riad Benguella (release squad announcement).
It was a release with a lot of good work in it and a few hard calls. Here’s what the role involves, and the decisions we made to keep the release on course.
What does an Editor Tech Lead do?#
Every major WordPress release is run by a squad of volunteers, each looking after one area. The Editor Tech Leads look after the block editor.
The editor is built separately, as the Gutenberg plugin, which releases every two weeks. Only some of that work is ready for any given WordPress release. With the feature leads, we decided what was ready to ship, got it into WordPress at each beta and release candidate, and kept on top of bugs until launch.
It also means holding the line. After the first beta only bug fixes go in, and the bar rises again at release candidate. Saying no to good work is part of the job.
What shipped?#
For people building sites, the headline features were these.
Font Library.
Install, upload and manage fonts from the editor, whatever theme you use. I made a short video walking through it.
Simpler link editing
I also worked on this feature with design lead Rich Tabor. My video on the changes shows how small tweaks made a big difference to something we all do every day.
Other notable features
- Revisions for styles, templates and template parts.
- Data views for pages, templates, patterns and template parts in the Site Editor.
- Background images and shadows as design tools.
For developers, 6.5 made the Interactivity API public and introduced the Block Bindings API. The release post covers the rest.
What were the hard calls?#
The hardest part of the role was deciding what was ready. Two decisions stand out.
Where should fonts live?
Late in the cycle, contributors were divided over where uploaded fonts should be stored. Some project leads wanted fonts in a folder of their own, because fonts aren’t media. Others worried that hosts with locked-down servers couldn’t adapt that close to release. Both positions were reasonable.
A compromise in early March tried to satisfy both. Feedback reopened the question two weeks later.
With launch days away, the squad chose the safest option and kept fonts in the uploads folder. A better home for them could wait for a future release.
That meant delaying the release by a week and adding an unplanned fourth release candidate. Nobody wants to move a launch date. Shipping a change that might break sites on some hosts would have been worse.
I ran the editor side of every 6.5 release candidate, including that extra one. It had to land the final Font Library changes days before launch without breaking anything else.
Pulling a feature
Synced pattern overrides let you change the content in one copy of a synced pattern without changing the rest. The feature was close, but it was causing side effects nobody had predicted. We pulled it from 6.5, and it shipped in 6.6 instead.
Pulling work late is hard on the people who built it. But as a lead, these are the difficult calls you have to make so the release as a whole goes smoothly.
Talking about 6.5 on WP Briefing#
WP Briefing is the WordPress project’s official podcast. On release day I joined Josepha Haden Chomphosy, then the project’s Executive Director, for episode 76, a preview of 6.5.
We talked about what the Editor Tech Lead role involves, then walked through the features I was most excited about. They included the Font Library, revisions, data views, the Interactivity API and the new link controls.
It was a good chance to explain the release, and the work behind it, to the wider WordPress community.
Looking back#
I’d push for wider review of big editor features much earlier. The concerns about fonts were valid, but they surfaced late, when they were hardest to resolve.
I also spent time making the release process easier for whoever came next, mostly through automation and clearer documentation. The squad also wrote up its own retrospective.
Thanks#
Riad was a great co-lead. I learned a lot from him. Thanks also to the editor triage leads, Anne McCarthy, Damon Cook and Fabian Kägy, and to the contributors who built and fixed everything that shipped.
If you’re thinking about volunteering for a release squad, do it. It’s hard work, and far more enjoyable than I expected. Ask me if you’d like to know what it’s like.


Comments
Nice work Dave 👊🏼