WordPress 5.5.1 maintenance release schedule

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.

Shortly after WordPress 5.5 “Eckstine” was released, a small handful of tickets were opened reporting identified bugs. Because a few of them are particularly inconvenient, 5.5.1 will be a short-cycle release so that they can be addressed more quickly.

After two 5.5.1 focused bug scrubs, the following release schedule is being proposed:

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). 1: Thursday August 27, 2020 at 20:00 UTC
Final release: Tuesday September 1st, 2020 at 15:00 UTC

The full list of the tickets targeted for this maintenance release is available on the 5.5.1 tickets report on Trac.

The 5.5.1 release is being lead by @audrasjb, @azhiyadev, @davidbaumwald, @desrosj, @johnbillion, @planningwrite, @sergeybiryukov, @whyisjake.

#5-5, #5-5-1

Jonathan Desrosiers 2:45 pm on August 26, 2020

I dropped by the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor meeting today and shared this proposed agenda. The team will work to find someone with availability to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. any bugs that can be included. The list currently targeted is here: https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+label%3A%22Backport+to+WP+Core%22+is%3Aclosed
stinkykong 3:29 pm on August 26, 2020

If my 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. report submitted 7 days ago shows it hasn’t been reviewed, do you think it will be included in the fix. Your message mentions a “few bugs” so I guess there weren’t many and then mine might have been addressed but it shows to be waiting review. https://core.trac.wordpress.org/ticket/51053#no0
- Jb Audras 10:27 pm on August 26, 2020
  
  Hi and thank you for your comment and for opening this ticketticket Created for both bug reports and feature development on the bug tracker.!
  
  This one was milestoned earlier today since the 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. has been reproduced by another contributor, but it won’t probably make it for 5.5.1 as it still needs 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.. It’s currently milestoned for 5.5.2, waiting for someone to propose a patch for this issue.
- stinkykong 7:55 pm on September 2, 2020
  
  Thank you for your response, @audrasjb

Comments are closed.

Welcome!

Communication

Share this: