WordPress 6.1.1 Planning

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Update 7 NOV 2022: Added @mamaduka as the Release Editor Tech Lead.

Update 9 NOV 2022: Added Bug Scrub for Thurs, Nov 10th.

Coming after the WordPress 6.1 release earlier this week, both @desrosj and I are planning to lead a 6.1.1 release for some fast-follow items that came up near the end of the 6.1 release cycle and have bubbled up post-release such that we would like to try and ship before the end-of-year holidays start to pull folks away from contributing. If there is a critical bugfix that has a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing./PR ready, then please look to add those to the 6.1.1 milestone in Trac or the WordPress 6.1.1 Editor Tasks project board in GitHub.

Schedule

The following schedule is what’s currently planned for the release, any additional 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. scrubs, release candidates, or other items will be added here as they get scheduled.

Friday, November 4th, 2022 at 13:00 UTC	Bug Scrub focused on finalizing items for 6.1.1 in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./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 be the repository owner. https://github.com/ (Slack archive)
Thursday, November 10th, 2022 at 17:30 UTC	Bug Scrub ahead of 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). (Slack archive)
Friday, November 11th, 2022 at 16:00 UTC	6.1.1 Release Candidate (Slack archive, ZIP download)
Tuesday, November 15th, 2022 at 17:00 UTC	6.1.1 Release Party

Team

Given the short timeline planned for this release, we are leveraging folks from the 6.1 release squad to help get 6.1.1 released in an expeditious manner. All others are welcome to help during bug scrubs, working on patches/PRs, testing patches/PRs, and participating in any release parties.

Release Coordinator: @jeffpaul

Release CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: @desrosj

Release Editor Tech Lead: @mamaduka TBD (if you’re interested and available, please reach out to @jeffpaul or @desrosj or comment on this post, thanks!)

Release Coordination

The #6-1-release-leads channel will continue to be used for all coordination and conversation related to the 6.1.x releases. This matches the pattern of communication that worked well for previous 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. cycles!

Additional 6.1.x Releases

The 6.1.1 release is the final release planned for 2022, a 6.1.2 seems feasible around the end of January but the Core team will want to look to confirm formal 6.1.x Minor Release Leads by then who can help shepherd future minor releases on the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (cc: @audrasjb @marybaum).

#6-1, #6-1-1, #minor-releases

Your point about it being too late to walk back the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor is valid, but @nodwsp is right that it should never have been made default. A toggle would have been VERY simply to build into the writing settings.

You draw people into WILLINGLY changing with the amazing features, not shove changes down their throat.

Everything WordPress has launched when it comes to block editor and FSE has been very very 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. level software that doesn’t have feature parity, is full of bugs and undergoes many iterations of breaking changes. This is completely unacceptable for production software. Users want stability, not shiny-new-object-syndrome.

There should be many more layers of QA between “a couple devs have played with this one feature” to “40% of the internet is now BETA testing”.

The end users are the only important measure and they’re completely absent in the process leading up to a full release.

The block editor is great but still somehow had a breaking change in 6.1. There’s 0% chance the FSE will be production ready before 2025 and it shouldn’t be marketed as such unless you want to continue pissing off your user base.

The people that are contributing are amazing but I’m sure none of them want to break users sites.

George Mamadashvili 3:19 pm on November 4, 2022

Happy to be Editor Tech Lead for this release.
- jeffpaul 2:36 pm on November 7, 2022
  
  Many thanks @mamaduka, could not be happier to have your help!
nodwsp 6:14 pm on November 4, 2022

Must STRONGLY remember you all, that we do NOT want the blocks (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/) editor by DEFAULT so there should be a switch to COMPLETELY disable it from adminadmin (and super admin) and frontend (dequeue styles and scripts)
- Marius L. J. 7:44 pm on November 4, 2022
  
  The blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor has been with WordPress since version 5.0, and there are no plans to change this. Although comments like this are quite disheartening towards the thousands of volunteers working on the software, you are of course free to use the Classic Editor plugin if you do not wish to use the block editor at this time.
  - Feast Design Co. 10:05 pm on November 7, 2022
    
    Your point about it being too late to walk back the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor is valid, but @nodwsp is right that it should never have been made default. A toggle would have been VERY simply to build into the writing settings.
    
    You draw people into WILLINGLY changing with the amazing features, not shove changes down their throat.
    
    Everything WordPress has launched when it comes to block editor and FSE has been very very 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. level software that doesn’t have feature parity, is full of bugs and undergoes many iterations of breaking changes. This is completely unacceptable for production software. Users want stability, not shiny-new-object-syndrome.
    
    There should be many more layers of QA between “a couple devs have played with this one feature” to “40% of the internet is now BETA testing”.
    
    The end users are the only important measure and they’re completely absent in the process leading up to a full release.
    
    The block editor is great but still somehow had a breaking change in 6.1. There’s 0% chance the FSE will be production ready before 2025 and it shouldn’t be marketed as such unless you want to continue pissing off your user base.
    
    The people that are contributing are amazing but I’m sure none of them want to break users sites.
    - Jonathan Desrosiers 4:34 pm on November 8, 2022
      
      These are all valid thoughts and concerns, but really off topic for the comments section on this post and will likely fall by the wayside because of that.
      
      After most releases, a call for retrospective thoughts is published. I think this type of feedback would fit in well there. Here is the 6.0 post for reference.
      - Jonathan Desrosiers 8:20 pm on November 9, 2022
        
        To follow up on this, the call for feedback on 6.1 has been published: https://make.wordpress.org/core/2022/11/09/wordpress-6-1-misha-retrospective/

Comments are closed.

Welcome!

Communication

Schedule

Team

Release Coordination

Additional 6.1.x Releases

Share this:

Site resources