Tag Archives: 7.1.1

Jb Audras 7:29 pm on September 2, 2026
Tags: 7.1.1, , ,   

Dev Chat summary: September 2, 2026

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, facilitated by @audrasjb 🔗 See the agenda post.

Announcements 📢

7.2

7.1.1

General

Discussion 💬

From @jeffpaul

Jeff resurfaced this heads up from @annezazu, for anyone who’s working on something for 7.2 to ensure they flag that to Anne for the roadmap post:

Howdy! I’m starting to work on a roadmap for WordPress 7.2 since we’re less than 2 months from 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. 1. I wanted to check in to see what might be coming up across the project that folks are dedicated to working on. As a reminder, roadmaps aren’t meant to be completely comprehensive but are meant to reflect the priority work slated for the release. As a result, I won’t include every little detail and instead focus on getting the broad strokes in place. As always, I’ll share drafts as I go but just want to flush out anything early as I have a long list already!

@annezazu – link to the Slack thread

@audrasjb: “On my side, I’d say this feature (ticket #65910) may be a huge thing for support teams (on dotorg as well as for plugins/themes support teams if we make it an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.). Design welcome but I think we can probably make a POC with the existing dashicons and basic styling.”

From @pbearne

Paul would love to see some of his patches that add tests get merged.

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

Adam Silverstein 5:00 am on September 2, 2026
Tags: , 7.1.1, ,   

WordPress 7.1.1 Release Schedule

Since WordPress 7.1 was released, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.org 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. https://wordpress.org/ Support Forums, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the 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. https://wordpress.org/gutenberg/ repository on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/. The volume and severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of tickets mean that the maintenance release should be prepared habitually.

This release will be co-led by @adamsilverstein, @adrianduffell, and @andraganescu.

Schedule

Date/TimeEvent
Thursday, September 3, 2026 at 14:00 UTCBug Scrub
Friday, September 4, 2026 at 14:00 UTCBug Scrub
Tuesday, September 8, 2026 at 20:00 UTCBug Scrub. WordPress 7.1.2 Milestone will be opened, and some tickets may be punted.
Wednesday, September 9, 2026 at 10:00 UTCBug Scrub
Thursday, September 10th, 2026 at 17:30 UTCWordPress 7.1.1 RC1
Tuesday, September 15, 2026 at 14:00 UTCBug Scrub.
Thursday, September 17, 2026 at 15:00 UTCWordPress 7.1.1 General Release

Note that the above times are estimates – exact times for scrubs, RCrelease 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). and General release will be announced in the 7.1 Release Leads room and will be based on availability of individuals helping with the release.

Targeted Fixes

WordPress 7.1.1 is intended as a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 7.1 cycle or intentionally deferred at the end of the 7.1 cycle. You can follow trac report 4 or the 7.1.x editor tasks board for proposed fixes.

Get Involved with 7.1.1

Bug Scrubs will happen in the #core room during the times posted above. Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, some locales have strings in 7.1 in need of translation.

General coordination for the release will happen in the 7.1 Release Leads room and decisions around code for the release will be made in the #core room.

Props to @jorbin and @adrianduffell for reviewing this post.

#7-1, #7-1-1, #7-1-x, #minor-releases

Aaron Jorbin 9:39 pm on August 20, 2026
Tags: , 7.1.1, ,   

Call for WordPress 7.1.x Release Managers

WordPress 7.1.0 was released August 19, 2026. While the work of a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. team includes people filling many different positions, maintenance release teams generally are considerably smaller, often 1–3 people. Minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. managers are responsible for:

  • Triaging bugs in coordination with committers and component maintainers.
  • Drafting announcements for the release.
  • Preparing for and running release day activities.
  • Updating the documentation on minor releases so that it gets better each time.

Members of the 7.1 release cohort are encouraged to stay on as release managers for maintenance releases, but it is not required to have been on a major release squad in order to be on a minor release team.

WordPress 7.1.1 will be scheduled based upon the severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. and quantity of bugs reported with a guesstimated release date between 1 September and 24 September. Please keep this timeline in mind when volunteering to be a release manager.

If you are interested in volunteering to be a release manager for the 7.1.x maintenance releases, please comment on this post or message me directly no later than 28 August.

Props to @joemcgill, @annezazu, @jeffpaul for reviewing this post before publication.

#7-1, #7-1-1, #7-1-x, #maintenance