Title: 5.3 – Make WordPress Core --- # Tag Archives: 5.3 [ ](https://profiles.wordpress.org/kirasong/) [Kira Schroder](https://profiles.wordpress.org/kirasong/) 8:16 am _on_ January 27, 2020 Tags: 5.3, [dev-notes ( 648 )](https://make.wordpress.org/core/tag/dev-notes/), [media ( 93 )](https://make.wordpress.org/core/tag/media/)    # 󠀁[Media Upload Request Flow in WordPress 5.3](https://make.wordpress.org/core/2020/01/27/media-upload-request-flow-in-wordpress-5-3/)󠁿 After a couple of questions from hosting companies about how to detect how well uploads are working at the server/request level, I thought further documentation would help. Here is a walkthrough of the request flow for media uploads, both before and after WordPress 5.3. Hopefully this will help with troubleshooting and debugging uploads on your infrastructure or sites! ## Before WordPress 5.3 Before WordPress 5.3, uploads had to complete during a single HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. POST request to `.../wp-admin/async-upload.php` or to the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application( think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/) with the media endpoint (`.../wp-json/wp/v2/media/`). 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 uses the REST API to upload, while any uploads outside the block editor ( or using the popup Media Modal) use `async-upload.php`. When uploads failed, they would return whatever HTTP error the server is set up to give (usually in the `5xx` range). This is usually due to timeout or resource exhaustion (like running out of memory) reasons. ## WordPress 5.3+ In WordPress 5.3+, uploads have been decoupled from a single request to allow for resuming. Now, when an upload returns a `5xx` error, there can be up to 5 followup requests. This is accomplished differently depending on whether `async-upload.php` or the REST API are used. ### Legacy Uploads Outside of the REST API, the upload happens first with a request to `async-upload. php`, just like before 5.3. If it fails, a request is made to `admin-ajax.php` with `form-data` containing ` action: media-create-image-subsizes` and `attachment_id: ####` to attempt to complete the action. If all retry attempts fail, the last request to `admin-ajax.php` has `_wp_upload_failed_cleanup: true` in `form-data` and attempts a cleanup. This deletes the the attachment post, the uploaded file, and any intermediate sizes that were created. Then, an error message is shown to users advising them to scale down the image and try uploading again. ### REST API Uploads When using the REST API, the initial request is to `.../wp-json/wp/v2/media?_locale =user`, and retry requests are to `.../wp-json/wp/v2/media/####/post-process?_locale =user` (where #### is the attachment post ID). If all attempts to resume post-processing fail with HTTP 5xx errors, the last is a standard “delete attachment” request, sent to `.../wp-json/wp/v2/media/####?force =true&_locale=user` with `X-HTTP-Method-Override: DELETE` headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. It performs the same cleanup as described for the `admin-ajax.php` upload method. Hopefully this helps in understanding how uploads work! If you have any questions, please ask in the comments for clarification. Thanks to [@azaozz](https://profiles.wordpress.org/azaozz/) for helping write this post! [+make.wordpress.org/hosting](https://make.wordpress.org/hosting) [#5-3](https://make.wordpress.org/core/tag/5-3/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#media](https://make.wordpress.org/core/tag/media/) [ ](https://profiles.wordpress.org/azaozz/) [Andrew Ozz](https://profiles.wordpress.org/azaozz/) 12:54 am _on_ January 8, 2020 Tags: 5.3, [retrospective ( 23 )](https://make.wordpress.org/core/tag/retrospective/) # 󠀁[5.3 Release Cycle Post-mortem](https://make.wordpress.org/core/2020/01/08/5-3-release-cycle-post-mortem/)󠁿 ## By the Numbers This cycle was longer, taking just over six months. The development (alpha) stage was 138 days, from May 8 to September 23. During that time there were 779 commits to 5.3 (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.). Most active committers were [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) with 426 (no surprises there), [@pento](https://profiles.wordpress.org/pento/) 66, [@afercia](https://profiles.wordpress.org/afercia/) and [@desrosj](https://profiles.wordpress.org/desrosj/) with 51 commits each. The “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.” stage started on September 23 and lasted for 23 days. There were 274 commits. Most active committers were [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) with 78, [@afercia](https://profiles.wordpress.org/afercia/) 42, [@desrosj](https://profiles.wordpress.org/desrosj/) 34, and [@whyisjake](https://profiles.wordpress.org/whyisjake/) with 24 commits. The “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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta).” stage started on October 16 and lasted for 27 days. There were 100 commits including documentation and build tools changes. Most active were [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) with 39, [@desrosj](https://profiles.wordpress.org/desrosj/) 20, and [@johnbillion](https://profiles.wordpress.org/johnbillion/) with 14 commits. There were 30 commits that were merged to the 5.3 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". after it was created on October 29. In total the release cycle lasted for 188 days and there were 1,153 commits. Looking at the numbers, the busiest time was during beta with an average of nearly 12 commits per day. For comparison there were only about 5.5 commits per day during the “alpha” stage [*](https://make.wordpress.org/core/tag/5-3/?output_format=md#footnote). ## Needed Improvements There were also some irregularities during the 5.3 cycle. * Many “new” bugfixes were committed during beta. _Generally these are added in alpha, and beta is reserved for testing and fixing any bugs introduced in alpha._ * Several apparent enhancements were committed from partially related bugfix tickets: [#34904](https://core.trac.wordpress.org/ticket/34904), [#47477](https://core.trac.wordpress.org/ticket/47477), [#47153](https://core.trac.wordpress.org/ticket/47153), etc. _Preferably there would be a discrete 1:1 relationship between tickets and changesets._ * Some code that would be considered “alpha” (mostly untested and non-reviewed) was committed during beta. _Preferably any code committed in beta is well-reviewed by multiple people with varied knowledge/experience with the existing code/areas of expertise._ A substantial departure from past releases was the inclusion of “global” CSSCSS Cascading Style Sheets. changes affecting all of the WordPress adminadmin (and super admin) during beta. They were committed from unrelated or partially related tickets: [[46241]](https://core.trac.wordpress.org/changeset/46241), [[46360]](https://core.trac.wordpress.org/changeset/46360), [[46244]](https://core.trac.wordpress.org/changeset/46244), and most of the other changesets marked as [“Improve and modernize user interface controls”](https://core.trac.wordpress.org/search?q=Improve+and+modernize+user+interface&noquickjump=1&changeset=on). It would have been preferable for the changes to be separated in new tickets, tested, reviewed, and then committed. Separating these into individual tickets would also have let enhancements be isolated and prepared for the next 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.. Individually, none of the irregularities listed above are a big problem, but when taken all together it introduced avoidable complexity. In this particular case, many small styling bugs were introduced during beta, which is far too late in the release cycle. Again, individually they were fixable, but their late introduction and lack of discrete ticketing left folks without enough time to find and fix them all. ## Moving Forward There are few steps that can be taken to avoid such irregularities in the future: * Add some “Release Cycle 101” to the developer documentation. This will ensure that people without prior experience are on the same page. Generally during alpha anything goes. Trunk can be broken and fixed every day as the contributors iterate on enhancements and bugfixes. Beta is for testing by the users and to fix the bugs that were introduced in alpha. 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta). is “we think it’s ready, find the edge cases!”  * Add a requirement for a code review for all changes committed during beta. Generally this has been the case for most commits during both alpha and beta. Requiring a review before merging works very well in 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/](https://wordpress.org/gutenberg/). It’s about time to make it “official” on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. too. * Remove the “(blessed)” part from the “task” ticketticket Created for both bug reports and feature development on the bug tracker. type on Trac. It seems it gives the wrong impression that a ticket can be “blessed” by anybody to allow it to bypass the release cycle rules. * Restrict use of the “task” ticket type on Trac only to the project leadership. Bypassing (our own) release cycle rules is not something that can be done lightly and carries a lot of responsibilities. Also, perhaps add a requirement for at least two reviews for each commit/code change in this case. * Perhaps extend the section on creating and using Trac tickets to specifically disallow unrelated or partially related changes to be made. This may be somewhat hard to determine, but when in doubt, better to create a new ticket instead of exponentially extending an existing ticket. In 5.3 there are several examples of such “run-away” tickets: [#47477](https://core.trac.wordpress.org/ticket/47477), [#47153](https://core.trac.wordpress.org/ticket/47153), [#34904](https://core.trac.wordpress.org/ticket/34904), etc. * The slower commit pace during alpha is partially due to new features being developed, and not committed until deemed “ready”. Another reason is perhaps that complex enhancements and 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. fixes need more research, reviews and testing before committing. Yet another reason is that perhaps most contributors focus more on the new features, enhancements and more complex bug fixes leaving the “easy” bugs for later. [#5-3](https://make.wordpress.org/core/tag/5-3/), [#retrospective](https://make.wordpress.org/core/tag/retrospective/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:10 pm _on_ December 17, 2019 Tags: 5.3, [minor releases ( 42 )](https://make.wordpress.org/core/tag/minor-releases/) # 󠀁[WordPress 5.3.2 Maintenance release schedule](https://make.wordpress.org/core/2019/12/17/wordpress-5-3-2-maintenance-release-schedule/)󠁿 Shortly after [WordPress 5.3.1 was released](https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/), a couple of high 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. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets were opened. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team immediately [scheduled two bug scrubs](https://make.wordpress.org/core/2019/12/15/wordpress-5-3-2-bug-scrubs-schedule/) to help these tickets moving forward. Main tickets addressed in 5.3.2: * Date/Time component: [#48957](https://core.trac.wordpress.org/ticket/48957) – Call to a member function `format()` on boolean in wp-includes/feed.php * Upload component: [#48975](https://core.trac.wordpress.org/ticket/48975) – Fix unhandled upper/lower case change in `wp_unique_filename()` * Media component: [#48960](https://core.trac.wordpress.org/ticket/48960) – Failed to open dir: No such file or directory in Windows * Build/Test tools component: [#48145](https://core.trac.wordpress.org/ticket/48145)– Random PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher test failures * Administration component: [#49003](https://core.trac.wordpress.org/ticket/49003)– Permalink buttons lack color contrast in most alternate color schemes For reference, see the [full 5.3.2 report on Trac](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&milestone=5.3.2&group=component&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&order=priority). [@azaozz](https://profiles.wordpress.org/azaozz/) [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/) will take care of this maintenance release as 5.3.2 is coming very shortly after 5.3.1 was released. Expected schedule for 5.3.2: * 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta). 1: Tuesday December 17, 2019 around 20:00 UTC (start of the release process) * Final release: Wednesday December 18, 2019 right before or after the devchat weekly meeting [#5-3](https://make.wordpress.org/core/tag/5-3/), [#minor-releases](https://make.wordpress.org/core/tag/minor-releases/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 1:16 am _on_ December 4, 2019 Tags: 5.3, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[WordPress 5.3 Retrospective Recap and Next Steps](https://make.wordpress.org/core/2019/12/04/wordpress-5-3-retrospective-recap-and-next-steps/)󠁿 The week of WP 5.3 release I posted a [call for feedback](https://make.wordpress.org/core/2019/11/15/5-3-retrospective-call-for-feedback/) for the development workflow. **Thank you to everyone that left their comments**! Reflecting on what worked and what didn’t is a great way to move forward together and steer the wheel if and when needed. Some comments didn’t follow the proposed format of start/stop/continue so it wasn’t very clear where they fit: I tried to put them in one of the categories. I also rephrased some feedback that was sometimes given as a positive statement (continue doing A instead of B) and sometimes a negative statement (stop doing B and do A). Finally, I added feedback I collected from the focus leads or from anonymous sources. If something doesn’t feel right let me know and I will amend the post. Read on for everyone’s feedback! [Continue reading →](https://make.wordpress.org/core/2019/12/04/wordpress-5-3-retrospective-recap-and-next-steps/#more-77868) [#5-3](https://make.wordpress.org/core/tag/5-3/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/davidbaumwald/) [David Baumwald](https://profiles.wordpress.org/davidbaumwald/) 10:56 pm _on_ November 20, 2019 Tags: 5.3, [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary: November 20, 2019](https://make.wordpress.org/core/2019/11/20/dev-chat-summary-november-20-2019/)󠁿 Here’s a summary of the November 20 Dev Chat ([agenda](https://make.wordpress.org/core/2019/11/20/dev-chat-agenda-for-november-20-2019/)/ [Slack archive](https://wordpress.slack.com/archives/C02RQBWTW/p1574283633109600)). ## Announcements ### The 󠀁[5.3 Retrospective – Call for Feedback](https://make.wordpress.org/core/2019/11/15/5-3-retrospective-call-for-feedback/)󠁿 post. [@clorith](https://profiles.wordpress.org/clorith/) asked, “Would it be an idea to also allow for an anonymous form to submit to that? I know some folks may not be comfortable with the potential for conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered _stale_, and will require a _refresh_ of the changes before it can be applied, or the conflicts will need to be _resolved_., and may feel safer giving an honest feedback if it wasn’t all public under their name? Then the feedback could be provided by the leads under a followup post, with no relation to individuals.” [@francina](https://profiles.wordpress.org/francina/) said she’d change the post to mention that anyone who’d like to give feedback privately is welcome to do so. 5.3 release leads [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/), [@youknowriad](https://profiles.wordpress.org/youknowriad/), [@justinahinon](https://profiles.wordpress.org/justinahinon/), [@audrasjb](https://profiles.wordpress.org/audrasjb/) also committed to offering the same. ## Upcoming Releases ### 5.3.1 [@whyisjake](https://profiles.wordpress.org/whyisjake/) offered the current list of tickets in the milestone at https://core.trac.wordpress.org/query?group=status& milestone=5.3.1 After a quick discussion of potential release dates, December 11, 2019 came out a potential winner. It’s pretty soon, but it still gives us time to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 5.3 regressions and bugfixes. That decision is not final – it’s pending more discussion in the comments. Got thoughts on timing? Please leave them in the comments – the sooner the better. While we see how those conversations shake out, [@audrasjb](https://profiles.wordpress.org/audrasjb/) graciously offered to lead the first 5.3.1 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. scrub on [Thursday November 21, 2019 18:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191121T1800) Next up: a call for volunteers to lead the release. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/), [@audrasjb](https://profiles.wordpress.org/audrasjb/), [@amykamala](https://profiles.wordpress.org/amykamala/), [@marybaum](https://profiles.wordpress.org/marybaum/), and [@whyisjake](https://profiles.wordpress.org/whyisjake/) all raised their hands. Everyone expressed great confidence in the potential candidates. Want to be part of the 5.3.1 release squad? Please leave a comment. ## Open floor [@youknowriad](https://profiles.wordpress.org/youknowriad/) brought up a discrepancy in the release cadence between WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/](https://wordpress.org/gutenberg/): > By December 11, the date proposed for a 5.3.12 release, Gutenberg will be ahead > of Core with about 5 releases and this is a problem. 12 Gutenberg releases shipped > into 5.3 . This is too much for a single WordPress release and with the current > schedule, it’s seems like this is going to be similar for 5.4. This is not tenable > for the future. It’s hard to stabilize and ship, it’s hard to summarize the changes > for third-party [developers] and users, it’s more scary to ship and people were > recommending the pluginPlugin A plugin is a piece of software containing a group > of functions that can be added to a WordPress website. They can extend functionality > or add new features to your WordPress websites. WordPress plugins are written > in the PHP programming language and integrate seamlessly with WordPress. These > can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party. to be installed for their clients( > and it’s risky since the plugin is a development plugin). So how to reduce that > gap is a big issue that needs solving IMO.Ideally I do think a shorter release > cycle for majors is better. (Why not just a 5.4 in like end of January). [O]therwise > we’ll have to include enhancements in minors. This generated a long discussion that continued well past the end of the Dev Chat. [See the full conversation starting here.](https://wordpress.slack.com/?redir=%2Farchives%2FC02RQBWTW%2Fp1574287107217800) _[@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) led the chat and wrote these notes. [@marybaum](https://profiles.wordpress.org/marybaum/) did some editing._ [#5-3](https://make.wordpress.org/core/tag/5-3/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 8:09 pm _on_ November 15, 2019 Tags: 5.3, [retrospective ( 23 )](https://make.wordpress.org/core/tag/retrospective/) # 󠀁[5.3 Retrospective – Call for feedback](https://make.wordpress.org/core/2019/11/15/5-3-retrospective-call-for-feedback/)󠁿 [5.3 “Kirk”](https://wordpress.org/news/2019/11/kirk/) was released on November 12, 2019. It was twelve weeks in the making, it had a big team behind it and the highest number of contributors ever. Congratulations to everyone! In order to prepare a retrospective post, I would like to ask everyone to leave some comments below with things they would like to bring up. To help, here are some questions to ask yourself: * What should WordPress **start** doing as a part of the development process? * What should WordPress **stop** doing as a part of the development process? * What should WordPress **continue** doing as a part of the development process? Please share your thoughts in the comments below! _Remember when commenting to keep the [discussion professional](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#comments) and focused on ways the process of creating WordPress is either already working great or can be improved._ Edited to Add: if you rather not give your feedback in a public space, please reach out to the following people on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). They are available to collect your feedback in a safe space, with no judgement and use it in the retrospective in an anonymous form: * [@francina](https://profiles.wordpress.org/francina/) * [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) * [@youknowriad](https://profiles.wordpress.org/youknowriad/) * [@justinahinon](https://profiles.wordpress.org/justinahinon/) * [@marybaum](https://profiles.wordpress.org/marybaum/) * [@audrasjb](https://profiles.wordpress.org/audrasjb/) [#5-3](https://make.wordpress.org/core/tag/5-3/), [#retrospective](https://make.wordpress.org/core/tag/retrospective/) [ ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/) 7:38 pm _on_ November 14, 2019 Tags: 5.3, [core-css ( 192 )](https://make.wordpress.org/core/tag/core-css/), [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/) # 󠀁[Dev Chat Summary: November 13, 2019](https://make.wordpress.org/core/2019/11/14/dev-chat-summary-november-13-2019/)󠁿 [@francina](https://profiles.wordpress.org/francina/) led this week’s dev chat – the last one of the 5.3 release cycle – [see the agenda here.](https://make.wordpress.org/core/2019/11/13/dev-chat-agenda-for-november-13-2019-post-5-3-week-1/) [For the full transcript, see the Slack archive here.](https://wordpress.slack.com/?redir=%2Farchives%2FC02RQBWTW%2Fp1573678812307400) Your faithful reporter: [@amykamala](https://profiles.wordpress.org/amykamala/). Let’s get going! ## Announcements [@francina](https://profiles.wordpress.org/francina/) opened Announcements with the release of [WordPress 5.3, which went live on November 12, 2019!](https://wordpress.org/news/2019/11/kirk/) She congratulated everyone, NOT just the folks active in the chat, on an amazing job. Several CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers were especially pleased that 5.3 came in on schedule (🎉) with the biggest group of contributors ever. Here are a few statistics: * 12 weeks of development * A release squad with nine focus leads, covering every relevant component that got an update * 645 contributors * 658 bugfixes * A new default theme, Twenty Twenty * Lots of fun and new friends made * And much, much more! Before release the squad counted at least 153 user-experience enhancements. ### Highlighted Posts The annual WordPress survey is open! Your feedback is not just appreciated – it’s vital to the future of WordPress. So please fill it out and share it everywhere you can think of. Tanking the floor for a moment, [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) told the group this survey is new – not the same as last year – and is broader. Whether you’re a contributor, designers, developers, users or hosts, please participate! Again, please [share the survey with anyone who touches WordPress in any way.](https://wordpress.org/news/2019/11/2019-annual-survey/) > [2019 Annual Survey](https://wordpress.org/news/2019/11/2019-annual-survey/) ## 5.3 Housekeeping Big thanks to everyone who has helped with testing so far! If that includes you, please keep testing and report any issues, concerns or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas in a [comment on Trac](https://core.trac.wordpress.org/). That’s how WordPress gets better and you get to shepherd your best ideas through the process. Need a refresher on how it works? [Here’s an outline of the post-release process.](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#post-release) [@francina](https://profiles.wordpress.org/francina/) wrapped the discussion with a note that in the next few weeks the release leads will open a call for retrospective. Want to share some honest, constructive feedback? That’ll be your chance! ## **5.3 Housekeeping Calls from component maintainers** [@francina](https://profiles.wordpress.org/francina/) opened the floor for component maintainers to bring up topics for discussion. [These are the components.](https://make.wordpress.org/core/components/) [@marybaum](https://profiles.wordpress.org/marybaum/) said “I love that we have a [#core-css](https://make.wordpress.org/core/tag/core-css/) channel. Does that mean Core CSSCSS Cascading Style Sheets. is a component?” [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) replied, “it’s closer to a focus than a component. Tickets can still be assigned to the affected component, eg Adminadmin (and super admin), Themes, etc. “ [@sergey](https://profiles.wordpress.org/sergey/) asked “If we have a `javascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)` focus, should we add one for CSS as well?  After a few more comments from folks, [@francina](https://profiles.wordpress.org/francina/) reminded all 30,000-plus potential attendees that we don’t make final decisions in devchat. She asked the folks talking about CSS to follow this process: * Make a proposal on the Core blogblog (versus network, site) * Discuss * Come to a conclusion * Act Here are the reports from other component maintainers: **[@williampatton](https://profiles.wordpress.org/williampatton/):** “Themes component is looking good. Prepping for next release.”  **[@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/):** “From the security team, now we have a Travis CI account that allows for private repos, we have the security tests running regularly. It should make it easier to find out if they’re passing during the release process.” and went on to ask [@sergey](https://profiles.wordpress.org/sergey/) if it was possible to add it to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. **@garret-eclipse:** “In the privacy component [@rogierlankhorst](https://wordpress.slack.com/team/U0TTA7Y2W) has [started work on a consent api](https://github.com/rlankhorst/wp-consent-level-api). ## Open Floor **[@mensmaximus](https://profiles.wordpress.org/mensmaximus/)** asked whether “we ever change the user management screen to a tabbed interface. What is the current state and what do core devs think?” **[@williampatton](https://profiles.wordpress.org/williampatton/) **started with a general reply: “There are lots of thoughts on redesign for user management, but lots of ideas mean lots of decisions [making it] hard to reach agreement.” [A lively discussion followed. ](https://wordpress.slack.com/archives/C02RQBWTW/p1573681586407900) Hopefully the WordPress world will see some new ideas for an even more usable Admin experience! _(Ed. note: The UXUX User experience discussion and the conversation below, about jQuery, happened at the same time, and you’ll see the comments jump from one to the other. Still, imo, both are worth your time and effort to decipher!)_ **[@enrico](https://profiles.wordpress.org/enrico/).sorcinelli** has “noticed that Juery’s `$` is no longer globally defined in admin.” That’s made some of their client sites cause issues with users’ code. [@clorith](https://profiles.wordpress.org/clorith/) answered, “The jQuery `$` being globally available was 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..” That bug got fixed in one of the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. updates in 5.3. “Although it’s not ideal, reports of issues are fewer than expected, and the code errors would be within the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. code,” [@clorith](https://profiles.wordpress.org/clorith/) continued, adding, “I tend to lean towards leaving it being the right thing.”  [Here’s the ticket they’re talking about](https://core.trac.wordpress.org/ticket/48568) and [the full discussion, including some observations on the future of jQuery.](https://wordpress.slack.com/archives/C02RQBWTW/p1573681576407400) **[@clorith](https://profiles.wordpress.org/clorith/)** noticed [two items leading the pack of recurring issues, 24 hours in:](https://wordpress.slack.com/archives/C02RQBWTW/p1573682348429900) * The update to add_submenu_page gives doing-it-wrong errors. We knew this, but devs weren’t prepared for users to have debugging enabled.  * The change to spread operators had plugins breaking, because things like custom walkers had dependencies on the previous operators. See the full discussion [starting at the link above. _(Ed. note: this highlighted test is the same link.)_](https://wordpress.slack.com/archives/C02RQBWTW/p1573682348429900) **[@pbiron](https://profiles.wordpress.org/pbiron/)** asked if anyone had reported problems with the new big-images or rotate-on-upload features.  **[@clorith](https://profiles.wordpress.org/clorith/)** and others[ noted very few issues.](https://wordpress.slack.com/archives/C02RQBWTW/p1573682564438600) [#5-3](https://make.wordpress.org/core/tag/5-3/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 2:47 am _on_ November 12, 2019 Tags: 5.3, [testing ( 26 )](https://make.wordpress.org/core/tag/testing/) # 󠀁[WordPress 5.3 RC 5](https://make.wordpress.org/core/2019/11/12/wordpress-5-3-rc-5/)󠁿 The fifth 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta). for WordPress 5.3 is now available for testing. WordPress 5.3 is currently scheduled to be released on **[November 12 2019](https://make.wordpress.org/core/5-3/)**. There are two ways to test WordPress 5.3 release candidate 5: * Try the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. (choose the “bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/tag/5-3/?output_format=md#trunk). nightlies” option) * Or [download the release candidate here](https://wordpress.org/wordpress-5.3-RC5.zip)( zip). For details about what to expect in WordPress 5.3, please see the [first](https://wordpress.org/news/2019/10/wordpress-5-3-release-candidate/), [second](https://wordpress.org/news/2019/10/wordpress-5-3-rc2/), [third](https://wordpress.org/news/2019/10/wordpress-5-3-rc3/) and [fourth](https://wordpress.org/news/2019/11/wordpress-5-3-rc4/) release candidate posts. Release Candidate 5 contains some 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. fixes for the new default theme, Twenty Twenty – for reference, see #48557 – and addresses the following tickets: * [#47708](https://core.trac.wordpress.org/ticket/47708) – 5.3 about page * [#48312](https://core.trac.wordpress.org/ticket/48312) – Fix a typo in an inline comment * [#48542](https://core.trac.wordpress.org/ticket/48542) – In `wp_default_packages_inline_scripts()`, make sure the root URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org middleware is registered before using the media middleware * [#48543](https://core.trac.wordpress.org/ticket/48543) – Comments: check if comment form element exists before adding a key handler to detect the cmd/ctrl-enter key press. * [#48517](https://core.trac.wordpress.org/ticket/48517) – Bundled themes: several changes to ensure consistency and accuracy for default theme headers * [#48518](https://core.trac.wordpress.org/ticket/48518) – Upload: When an image was scaled because it is larger than the big image threshold, use the originally uploaded image’s dimensions in `wp_get_missing_image_subsizes()`. Fixes an edge case/inconsistent behaviour when a registered image sub-size is also larger than the big image threshold. ## Plugin and Theme Developers Please test your plugins and themes against WordPress 5.3 and update the _Tested up to_ version in the readme to 5.3. If you find compatibility problems, please be sure to post to the [support forums](https://wordpress.org/support/forum/alphabeta/) so we can figure those out before the final release. The [WordPress 5.3 Field Guide](https://make.wordpress.org/core/2019/10/17/wordpress-5-3-field-guide/) has also been published, which details the major changes. ## How to Help Do you speak a language other than English? [Help us translate WordPress into more than 100 languages!](https://translate.wordpress.org/projects/wp/dev) _**If you think you’ve found a bug**, you can post to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta) in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, [file one on WordPress Trac](https://make.wordpress.org/core/reports/), where you can also find [a list of known bugs](https://core.trac.wordpress.org/tickets/major)._ [#5-3](https://make.wordpress.org/core/tag/5-3/), [#testing](https://make.wordpress.org/core/tag/testing/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 11:17 pm _on_ November 6, 2019 Tags: 5.3, [CSS ( 10 )](https://make.wordpress.org/core/tag/css/), [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [twentytwenty ( 6 )](https://make.wordpress.org/core/tag/twentytwenty/) # 󠀁[Dev Chat Summary: November 6, 2019 (5.3 week 12)](https://make.wordpress.org/core/2019/11/06/dev-chat-summary-november-6-2019-5-3-week-12/)󠁿 This post summarizes the weekly dev chat meeting from November 6th 2019 ([agenda](https://make.wordpress.org/core/2019/11/06/dev-chat-agenda-for-november-7-2019-5-3-week-12/)/ [Slack archive](https://wordpress.slack.com/archives/C02RQBWTW/p1573070435436500)). ## Announcements [WordPress version 5.3 Release Candidate 4 was released](https://wordpress.org/news/2019/11/wordpress-5-3-rc4/) on Tuesday 5th. Everyone please help by testing out the 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta).. ## Upcoming Releases – 5.3 [@joyously](https://profiles.wordpress.org/joyously/) asked where to look to see how translations are going for WordPress 5.3. [@mapk](https://profiles.wordpress.org/mapk/) shared the link to the [project summary on Translate](https://translate.wordpress.org/projects/wp/dev/). [@collet](https://profiles.wordpress.org/collet/) raised some issues discovered on Twenty Twenty: * One issue related to nested rules in full-width Group & Cover blocks: [965](https://github.com/WordPress/twentytwenty/issues/965). * Four issues related to column 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.: [960](https://github.com/WordPress/twentytwenty/issues/960), [961](https://github.com/WordPress/twentytwenty/issues/961), [962](https://github.com/WordPress/twentytwenty/issues/962) and [963](https://github.com/WordPress/twentytwenty/issues/963). * One issue related to nested blocks on starter content: [#959](https://github.com/WordPress/twentytwenty/issues/959) * Also mentioned [a pull request (701)](https://github.com/WordPress/twentytwenty/pull/701) that would be a worth inclusion in 5.3 [@johnbillion](https://profiles.wordpress.org/johnbillion/) answered Twenty Twenty can be updated independently of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. It’s ultimately up to the team behind the theme to decide if any of these bugs need to go into Twenty Twenty before 5.3 is released, or whether they can wait until 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. release of the theme. [@anlino](https://profiles.wordpress.org/anlino/) will take a look at fixes for the columns issues today and tomorrow. Hopefully he can get those fixes before 5.3 final release. If there isn’t time to get them tested and merged properly, at least we’ll have the fixes good to go post-release. The issues will be discussed in [Twenty Twenty GitHub repository](https://github.com/WordPress/twentytwenty) and in the _core-themes_ and _core-editor_ SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channels to see what can land in time for final release of 5.3. [@collet](https://profiles.wordpress.org/collet/) also mentioned an issue related to the About page. In the about page. it’s said that “Heading blocks now offer controls for text and background color”. However, there is no control to change the background color inside the editor. It doesn’t appear to be related to Twenty Twenty. It needs to be updated in the About page. Finally, [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) asked for more testing concerning a recent post published on Make/Core: [Use of the “wp_update_attachment_metadata” filter as “upload is complete” hook](https://make.wordpress.org/core/2019/11/05/use-of-the-wp_update_attachment_metadata-filter-as-upload-is-complete-hook/) ## Open floor [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) asked if a _core- css_ channel could be created on Make WordPress Slack team to discuss CSSCSS Cascading Style Sheets. stuff. Given the amount of positive reactions, the Slack channel was immediately created by [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) 💥🕺💃 [@mpcube](https://profiles.wordpress.org/mpcube/) asked for a review on ticketticket Created for both bug reports and feature development on the bug tracker. [#48506](https://core.trac.wordpress.org/ticket/48506). Discussion to continue in the proper ticket. ### Move Dev chat meeting time (end of daylight saving time) [@audrasjb](https://profiles.wordpress.org/audrasjb/) asked for a final decision about moving the dev chat meeting time with end of daylight savings time (DST). The meeting attendees agreed to move it from 20:00 UTC to 21:00 UTC starting on Wednesday 13th November. The New Contributor Meeting will also move from 19:00 UTC to 20:00 UTC. _These notes were taken by [@audrasjb](https://profiles.wordpress.org/audrasjb/) and proofread by [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)_ [#5-3](https://make.wordpress.org/core/tag/5-3/), [#css](https://make.wordpress.org/core/tag/css/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#twentytwenty](https://make.wordpress.org/core/tag/twentytwenty/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:57 pm _on_ October 30, 2019 Tags: 5.3, [contributor day ( 17 )](https://make.wordpress.org/core/tag/contributor-day/), [wcus ( 6 )](https://make.wordpress.org/core/tag/wcus/)    # 󠀁[Dev Chat Summary: October 30th 2019](https://make.wordpress.org/core/2019/10/30/dev-chat-summary-october-30th-2019/)󠁿 This post summarizes the weekly dev chat meeting from October 30th 2019 ([agenda](https://make.wordpress.org/core/2019/10/30/dev-chat-agenda-for-october-30-2019-5-3-week-11/)/ [Slack Archive](https://wordpress.slack.com/archives/C02RQBWTW/p1572465617010300)). ## Announcements [WordPress version 5.3 Release Candidate 3 was released on Tuesday](https://wordpress.org/news/2019/10/wordpress-5-3-rc3/). Everyone please help by testing out the 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta).. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor team released [Gutenberg version 6.8](https://make.wordpress.org/core/2019/10/30/whats-new-in-gutenberg-30-october/). ## Dev chat meeting time Like every year, with end of DST (daylight saving time), the meeting time should be moved from 20:00 UTC to 21:00 UTC. Two options are proposed: * Moving on Wednesday November 13th (the day after WP 5.3 is going to be released) * Moving on Wednesday November 20th (one week later) Please share your thoughts in this post’s comments. ## WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. 󠀁[Learn more](https://central.wordcamp.org/about/)󠁿. US Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 WordCamp US’s contributor day is planned for Sunday 3rd November. `5.3` was branched last week, so contributors will be able to work on WordPress 5.4 milestone since `trunk` is now version `5.4-alpha`. [@earnjam](https://profiles.wordpress.org/earnjam/) and [@wpscholar](https://profiles.wordpress.org/wpscholar/) will be leading the core table, Helping people get set up, learn how to get started, find places to focus on work, etc. They also should have several component leads present that can split off and focus on their areas for people who are interested. ## Upcoming Releases WordPress 5.3 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)](https://make.wordpress.org/core/tag/5-3/?output_format=md#alpha-beta). 4 is scheduled next Tuesday if needed. There is still 7 tickets open [in the milestone](https://core.trac.wordpress.org/query?status=reopened&status=assigned&status=reviewing&status=new&status=accepted&group=status&milestone=5.3). * 2 are tasks: [#48231](https://core.trac.wordpress.org/ticket/48231) and [#47708](https://core.trac.wordpress.org/ticket/47708) * 5 are new tickets opened for possible regressions: [#48451](https://core.trac.wordpress.org/ticket/48451), [#48453](https://core.trac.wordpress.org/ticket/48453), [#48458](https://core.trac.wordpress.org/ticket/48458), [#48466](https://core.trac.wordpress.org/ticket/48466) and [#48469](https://core.trac.wordpress.org/ticket/48469) [@azaozz](https://profiles.wordpress.org/azaozz/) regrets that things weren’t reported much earlier, during 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.. By the way, two tickets have patches already, one is almost there, and one may be a candidate for 5.3.1. As 5.3 was branched, all fixes are probably going to be committed to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. (5.4-alpha) but hold on on merging to 5.3 for couple of days to allow easier testing and review. All are (possible) regressions with the way some plugins use particular hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. around image post-processing and image metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. updates. [@joyously](https://profiles.wordpress.org/joyously/) reported [a feedback found in Alpha/Beta support forum](https://wordpress.org/support/topic/setattributes-does-not-work-as-expected-with-two-or-more-post-meta-fields/). It was [already merged to Gutenberg](https://github.com/WordPress/gutenberg/pull/17455) and looks fixed in 5.3 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 code. [@youknowriad](https://profiles.wordpress.org/youknowriad/) was pinged as Editor focus lead for WP 5.3. ## Open floor [@joyously](https://profiles.wordpress.org/joyously/) asked about backporting security fixes to old versions request’s status. [@clorith](https://profiles.wordpress.org/clorith/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/) noted [there will be a panel session at WordCamp US](https://2019.us.wordcamp.org/session/automated-updates-panel/). For those who are not attending WordCamp US, [questions can be sent via Twitter](https://twitter.com/JosephaHaden/status/1188938921150861312). [@desrosj](https://profiles.wordpress.org/desrosj/) added that there was a very large amount of feedback. [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) and others are working to compile all that feedback so that all of it can receive proper consideration. [#5-3](https://make.wordpress.org/core/tag/5-3/), [#contributor-day](https://make.wordpress.org/core/tag/contributor-day/), [#wcus](https://make.wordpress.org/core/tag/wcus/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/5-3/page/2/?output_format=md)