Dev chat summary: March 17, 2021

@francina led the chat on this agenda.

Announcements

The big news: WordPress 5.7 “Esperanza” landed March 9, and the group took a well-deserved bow.

Moving on, Francesca highlighted these posts:

@jeffpaul noted Trial run: Consistent minor release squad leaders for each major branch. Francesca added that the post is both a highlight and a call for volunteers.

@annezazu put out a last call for FSE Program Testing Call #3: Create a fun & custom 404 page. If you’d like to catch up on the previous two FSE tests, Anne and Francesca said you can find previous calls under this tag. If you’d like to do your own testing, the FSE Handbook has a page with instructions. Capping off the FSE discussion was Marketing Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @webcommsat, who said you can also share this LinkedIn promotion.

@francina then turned to posts that need feedback. This Proposal: A WordPress Project Contributor Handbook drew spirited emoji support from the group. Francesca also reminded the group to sign up for the Updates blog to keep up with a variety of team updates, as well as posts from @chanthaboune about cross-team efforts and the latest news from leadership.

Components check-in and status updates

@sergeybiryukov started with jQuery news: the version in 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. has updated to 3.6.0, which is mostly 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 and improvements. Two callouts:

Aside from the change to no longer ensure XHTML-compliant tags for you, we do not expect other compatibility issues when upgrading from a jQuery 3.0+ version.

See ticketticket Created for both bug reports and feature development on the bug tracker. #52707 for more details.

 jQuery hoverIntent library has updated from version 1.8.3 to 1.10.1. The changes all appear to be minor.

See ticket #52686 for more details.

@adamsilverstein checked in with Media news: he’s working on landing support for WebP images in 5.8 and would like testing and feedback on ticket #35725.

Up next, @audrasjb said he has nothing new for Menus and WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user., but he’s quietly scrubbing bugs and watching tickets. On Upgrade/Install, he highlighted this feature plugin proposal post.

@sabernhardt wrapped up the Component updates with his announcement of a Toolbar triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./bug scrub for the following day, March 18, at 16:00 UTC.

Open floor

IE11 support

@adamsilverstein asked: Given that the Project has decided to drop support for IE 11, have we discussed a specific release to make that change in?

The discussion that followed outlined a general process—notify, then act—but pointed out the group still needs to make a specific plan for IE11. Adam noted that IE11 is the only major browser that doesn’t support WebP images.

@desrosj said there might already be a notification in place. @adamsilverstein found a ticket, #48743, to that effect. Further discussion also made it clear that the team needs to do more to announce the change, including stronger language in relevant tickets (@desrosj and @audrasjb), a News blogblog (versus network, site) post (h/t: @jorbin) and relevant Handbook updates (h/t @jeffpaul)

“Try FSE?”

@sergeybiryukov observed:

It seems that most of WP users (outside of the contributing teams) are still largely unaware that full-site editing is coming later this year.

Perhaps that’s intentional, but once we have something stable to test, have we considered adding a dashboard widget to one of the upcoming minor releases, to invite more users to test FSE before final release, like we did with 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/ in #41316 for WP 4.9.8?

See the full discussion that followed, with a variety of people sharing a variety of views on the subject.

#5-7-1, #5-8, #core, #dev-chat, #meetings, #summaries, #summary

Dev chat Meeting Summary: 17 Feb 2021

Full meeting on Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/.

Main discussions from 05:00 meeting:

  • @afragen: the Rollback Update Failure repo (here)
  • @tellthemachines: CSSCSS Cascading Style Sheets. themed 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 in #core-css (here)

Announcements

5.7 -related

  • 5.7 Beta 3 is here! Thanks you for testing, and to all the awesome people who have been tirelessly working on making WordPress happen—even going into this second year of pandemic.
  • WordPress 5.7 Docs Focus update: @audrasjb
    • Several dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are just about ready, pending final review from component maintainers or by the corresponding ticketticket Created for both bug reports and feature development on the bug tracker. authors.
    • A list of the HelpHub pages that need updates once 5.7 launches.
    • If you worked on a ticket labelled needs-dev-note, or if you want to work on a devnotedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., please get in touch with @audrasjb to keep everything coordinated. (Ed. note: And the release squad knows where to send your props!)
  • Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is still planned for RC1 next week. Co-ordinating with component maintainers taking place.

Minor releases

WordPress 5.6.2. RC 1 now available – @desrosj 5.6.2 

  • This one is a very small release, and the majority of the bug testing could be done in 10-15 minutes.
  • Additional testing available, raise tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets if any issues found. Focus to continue on 5.7
  • 5.6.2 will be pushed out on Monday 22 February 2021.
  • Aim is to try out a much smaller 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., which fixes a small handful of user-facing bugs that were finished and ready to go.
  • If it’s received well, we could potentially explore more frequent, smaller minor releases.
  • If you have any feedback around that, please feel free to share with @chanthaboune, @desrosj, or one of the Core team reps.

What’s new 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/ 10.0.0

  • Version 10.0 is here!
  • It landed on 17 February 2021 and marks 100 releases of Gutenberg.
  • Congratulations to the Gutenberg team and all contributors involved.

Highlighted posts

Here are the latest 5.7 dev notes: 

Core editor front:

Full Site Editing:

  • work is going strong. Test, give feedback, ask friends to try it if they have never seen WP before and write down (with their consent of course) how they interact with the UIUI User interface, how does the UXUX User experience feels, etc.
  • @annezazu: The #fse-outreach-experiment needs you, no matter what you do with WordPress. The next call for testing will likely be this week, alongside a comprehensive update that follows the open submission for questions related to FSE.
  • If you want to test now, use this “How to Test” handbook page for FSE testing, and please share your feedback. (Though you don’t have to!)
  • Discussion: how to get more people sending feedback and asking questions, especially from people who do not follow the Core blogs.
    • @francina: raised questions on how to get more part, particularly students and meetups
    • @webcommsat: In Marketing, we are also helping non-tech users understand better what is happening on FSE and the benefits it will bring. This will help with future marcomms too. If anyone from a non tech background would like to add to the discussion session from this week, contact the Marketing Slack for the documents. We also work with community on newsletters and social to Meetups.
    • @timothyblynjacobs: Should we consider doing another Core dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user./callout like was done for 5.0?
    • @nalininonstopnewsuk: request to let Marketing know please if this is planned at a future date to include in the schedule. 
    • @annezazu: Latest call for questions is closed, 47 questions received. There will be future rounds for open questions so we can continue to refine the general ‘reach’ going forward.
    • @lukecarbis: We’re starting to think about restarting meetups here in Australia, so maybe we could even do some in-person click-around testing, if there is a script.
    • Where is the best place to encourage outreach on this— #fse-outreach-experiment (not a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. channel) or somewhere else? @annezazu suggested #core-editor channel on Slack. @Clorith suggested FSE-outreach channel to get testing and feedback on the feature before it lands in core.
  • Discussion to continue after the meeting.
  • A Week in Core – February 15, 2021 
  • Making WordPress Releases Easier from @chanthaboune.

Updates from component maintainers

Build/Test Tools update – Updates shared by @sergeybiryukov

  • Single-and Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site PHPUnit test runs on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Actions are now separate jobs so they run in parallel and finish faster. Total duration was ~26 minutes; now it finishes in ~16 minutes. Thanks @johnbillion. Ticket #52548: Run Multisite tests in parallel during CI for more details.
  • Work keeps going to add missing @covers tags to PHPUnit tests, for better tracking of coder coverage. Ticket #39265: Missing @covers in the comment blocks in PHPUnit tests for more details.

General: noindex robots 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. tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) was added to search results, to keep search engines from indexing internal search results (and guard against reflected web spam attacks). Ticket #52457: WordPress vulnerable to search-reflected webspam for more details.

Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week 

More from Build/Test Tools@desrosj
The GitHub Action workflow files are now backported all the way through 3.7, to bring back automated testing for those branches if they need a security release. He will publish a post with the overall status of the work on 18 February. 

Upgrade/Install:

@fragen: Feature plugin Rollback Update Failure needs testing—just install and activate.

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/ or can be cost-based plugin from a third-party will create a zip of the current plugin/theme version in wp-content/updates/rollback. The first test: check whether or not the process uses too many server resources. Does it cause a server timeout? There’s a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to simulate a failure.

@audrasjb  shared major news: @afragen has joined us as component maintainer

General component news:

@francina: Has started reaching out to component maintainers, both to gauge the situation of features/tickets for 5.8 and check how many are active. Those who aren’t will be moved to an emeriti status, like the one used for committers, as Josepha illustrated in the post Committers, Maintainers, and Emeriti

If you:

Open Floor 

@Eclev91: Raised ticket #43495: Use Semantic Versioning for releases and asked for it to be reopened. “I’ve reviewed the discussion that took place in Slack that prompted the ticket, which noted that because core is currently on a base-10 versioning system, new and ready-to-launch features like ServeHappy and GDPR were blocked behind Gutenberg development slated for 5.0 (the idea of a 4.10 to launch these features was unheard of and untested). I added my thoughts to the ticket outlining a variety of QOL improvements for both core development and core consumers (devs like myself who maintain many WP sites) that could be gained by moving to semantic versioning. I imagine folks with hosting companies working on automating updates would also have $.02 to add.” If anyone has feedback, please post it in the Trac ticket.

Testing instructions

  • @justinahinon: a WordPress testing instructions document was drafted at the 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/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at Yoast (doc). Feedback about toning, phrasing, etc requested. Views on how it could work with the Core Handbook User Testing guide.
  • @jeffpaul: suggested a potential use could be in Make WordPress Test Handbook rather than the Core handbook .
  • @desrosj: this document is one that will be impossible to maintain over time. But it looks like each of the items you’ve detailed here so far look like great E2E test cases!
    • Some of these use cases could be used for user testing at meetups, or any other group of people that want to work on something together.
    • The steps change far too often release to release, and unless someone owns updating this document (or page) with each release, it will quickly become outdated. But if each of these are a test case, then they will fail when changes occur.
    • Not trying to discount having a document for testing at all! But feel this is far too detailed/intricate to maintain effectively for that purpose. 
    • @justinahinon: But if each of these are a test case, then they will fail when changes occur.

Growing Make Test Team

  • @francina: Interest in reviving the Test Team. It has been dormant for a while: no team reps, no chats.
  • During 5.6, @monikarao and others started weekly test scrubs.
  • @jeffpaul: queried whether weekly test scrubs were enough to consider people as leading the Test Team into action again. Worth encouraging.
  • Discussion: agreed.
  • @Desroj: Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. team actually falls under the Test team’s umbrella now. Results of that team’s efforts are usually posted to each individual ticket as we go through them. But that is just one form of testing.
  • We have a group of dedicated people showing up every week and that is amazing. At least one person on the team scrubs tickets present on a nearly daily basis.
  • @nalininonstopnewsuk: we are planning a promote a team every month idea in marketing. If you decide to put a plea out for testing team, let us know to feature it in the schedule. Agreed.

Thanks to @nalininonstopnewsuk, @webcommsat. and @marybaum for the dev-notes this week.

#5-7, #core, #dev-chat, #summaries, #summary

Test Scrub for WordPress 5.7 and office hours

As part of the 5.7 release, we’ll be hosting a focused test scrub for the below-listed tickets, February 12, 2021 13:30 UTC in the #core channel on 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/..

UTC in the #core channel on Slack.

https://core.trac.wordpress.org/ticket/52473
https://core.trac.wordpress.org/ticket/52477
https://core.trac.wordpress.org/ticket/52433
https://core.trac.wordpress.org/ticket/52452
https://core.trac.wordpress.org/ticket/43890
https://core.trac.wordpress.org/ticket/46601

The ticketticket Created for both bug reports and feature development on the bug tracker. is ready to be considered for commit but needs testing/QA.

To set up the Testing Environment follow the steps listed here – https://meta.trac.wordpress.org/ticket/5581#comment:3

How to apply 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.

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket, for example 35449

npm run grunt patch:35449

How to fetch and then checkout a PR, for example, PR 828

git fetch upstream pull/828/head:pr-828
git checkout pr-828

or for PR:

npm run patch https://github.com/WordPress/wordpress-develop/pull/828

Check the handbook for more ways to test patches.

Do you have a ticket you want to bring up for testing?

Fantastic!

In order to allow testers to manually test the patch, you should include the following information:

  • What are the steps to reproduce the problem?
  • What are the steps to test?
  • Are there any testing dependencies such as a 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/ or can be cost-based plugin from a third-party or script?
  • What is the expected behavior after applying the patch?

#5-7#test#testing

Media Meeting Recap – January 28, 2021

The following is a summary of the weekly Media component meeting that occurred on Thursday, January 28, 2021 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @paaljoachim, @hellofromtonya, @joedolson, @ricjcs, @audrasjb, @mista-flo, @mkaz, @chaion07

Open Floor

This meeting’s focus began with an open floor for discussion on outstanding tickets and issues members wanted to address.

#47839: Extended file management in Media Library – @ricjcs brought up this ticketticket Created for both bug reports and feature development on the bug tracker. containing design samples of what folders could look like in the media library. Discussion occurred around what this feature would entail from a backwards compatibility perspective.

#52372: Ability to Replace image on the “attachment details” screen – This feature has been explored and ultimately closed after this comment in #49096. Per @antpb, “This is another one where I don’t think it’s a bad idea, in fact, it’s great, but it’s very much in 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/ or can be cost-based plugin from a third-party territory to make the decisions for your individual site. What may be good for one site may not be good for all. Offering the ability to replace media by default offers folks ways to unintentionally break old content.”

5.7 Tickets

#52192: 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/.: Add batch image editing This ticket is currently in review with @antpb and is aiming to be committed before alpha. It was discussed that this endpoint is low risk as it does not impact any existing endpoints and adds new ones.

#50025: Media Library not showing new uploads when filtering by date – This ticket is currently in review after it was found to have issues with the classic 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. media flow. @antpb is testing and will be aiming to commit before alpha.

#39004: Alt attributes should be searchable in media library – This ticket was discussed as being close to ready for commit, but talks after the meeting indicate it may need further testing with larger media libraries.

#52387: adjacent_image_link returns a link with no accessible text@antpb has given an initial review and is aiming to commit soon after more testing.

Bug Scrub

There are a number of enhancement tickets that still need to be scrubbed. 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. scrub has been scheduled for Monday, February 1 at 16:00 UTC to go over these tickets. Please join us if you would like to contribute!

Props @antpb for proofreading and final review.

#core, #media, #summary

Test Scrub for WordPress 5.7 and office hours

As part of the 5.7 release, we’ll be hosting a focused test scrub for the below-listed tickets, Tomorrow, Friday 29/01/2021 13:30 UTC in the #core channel on 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/..

https://core.trac.wordpress.org/ticket/51812
https://core.trac.wordpress.org/ticket/51941
https://core.trac.wordpress.org/ticket/52355
https://core.trac.wordpress.org/ticket/48562
https://core.trac.wordpress.org/ticket/47912

The ticketticket Created for both bug reports and feature development on the bug tracker. is ready to be considered for commit but needs testing/QA.

To set up the Testing Environment follow the steps listed here – https://meta.trac.wordpress.org/ticket/5581#comment:3

How to apply 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.

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket, for example 35449

npm run grunt patch:35449

How to fetch and then checkout a PR, for example, PR 828

git fetch upstream pull/828/head:pr-828
git checkout pr-828

or for PR:

npm run patch https://github.com/WordPress/wordpress-develop/pull/828

Check the handbook for more ways to test patches.

Do you have a ticket you want to bring up for testing?

Fantastic!

In order to allow testers to manually test the patch, you should include the following information:

  • What are the steps to reproduce the problem?
  • What are the steps to test?
  • Are there any testing dependencies such as a 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/ or can be cost-based plugin from a third-party or script?
  • What is the expected behavior after applying the patch?

#5-7#test#testing

#5-7, #test, #testing

Dev chat summary: January 21, 2021

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team postponed the afternoon dev chat for 24 hours to get past the US presidential inauguration. @metalandcoffee, aka Ebonie Butler, led the meeting on this agenda.

Announcements and highlighted posts

@metalandcoffee brought the group’s attention to these items:

Ebonie also invited the group (and you, too, dear reader!) to stop by a 5.7 test scrub. There’s one every Friday at 13:30 UTC.

Releases

The Core team is busy with one minor and one 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.

WordPress 5.6.1

5.6.1 has a squad and is deciding on a date; here are the tickets for the milestone.

WordPress 5.7

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 lands on February 2. Here are the tickets in the milestone.

Per @hellofromtonya, aka Tonya Mork, noted there are 66 open features and enhancements that need committing or punting by Beta 1. (Ed. note: Beta 1 imposes a feature freeze on the release. After that, commits are 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 only. RC 1 imposes a string freeze, so Polyglots can finish translations before final release.)

Tonya had more to share about the milestone tickets. See the full discussion and consider pitching in on some tickets, especially, as @metalandcoffee pointed out, if there’s something you really want to see in the release.

Updates from component maintainers

@sergeybiryukov kicked off the updates with a general announcement that as of January 21, WordPress Core has more than 50,000 commits and thanked every past, present and future contributor.

Sergey also reported in for Polyglots, which added support for Austria to remove_accents() in #49967.

@audrasjb reported in that Menus has two tickets ready for commit. In Upgrade/Install, JB recognized @dd32, aka Dion Hulse, for his helpful insights on rollbacks.

In Design, @estelaris, aka Estela Rueda, asked for testing to review this Core color-change pull request, based on a discussion in the Design channel that was happening at the same time as devchat.

@xkon reported in from Privacy, saying he’s pretty sure they’ll be punting some tickets from 5.7 that need more iteration. The team also expects inputs from other teams, which happens a lot with privacy.

Agenda comments

jQuery UIUI User interface and #52163

Between standard reports and Open Floor, devchat takes up items people add to the comments on the Agenda post—and other items people specifically add.

That happened with a question @hellofromtonya had on ticketticket Created for both bug reports and feature development on the bug tracker. #52163, which is about updating jQuery UI and removing jQuery migrate. All of that is getting punted to 5.8, but at the moment there’s no firm timeline for the new jQuery UI release. Follow the discussion as it happened here.

Consolidating instructions for local dev environments

Across the WordPress Project you can find several sets of instructions that will walk you through setting up a local development environment for building WordPress sites, themes, and plugins; contributing to all of those things plus Core; and doing lots of different kinds of testing.

Those local-environment instructions vary widely in age, approach and tooling.

@paaljoachim has started a Meta ticket (as opposed to a normal ticket) to discuss consolidating those instructions and would very much like feedback, comments and people to brainstorm with.

So far, @desrosj and @hellofromtonya have offered help. But this is a big, complicated thing — so please pitch in!

WordPress Importers

@pento offers this proposal to modernize the WordPress Importers, complete with a slew of links.

As he told the group, “

There’s a lot to read, but I’d appreciate folks taking the time to go through it. :slightly_smiling_face:2:44Much of it is fairly sensible, but the last post in the series does contain a proposal for writing exporters for CMSes that don’t provide an export option, which is a departure from our usual approach.”

See the real-time discussion here.

Visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. tests

@isabel_brison has a pull request that sets up visual regression testing in Core. The TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket is #49606.

@francina raised the point that some hosts are starting to do visual regression. See that discussion here.

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.-based navigation

@metalandcoffee: “Daniel Richards wanted to let everyone know that work on the block-based Navigation screen has picked up again, and there’s a new channel for [it] ” — #feature-navigation-block-editor.

Here’s the GitHub project.

Thoughts on browser versions?

@desrosj would like some feedback on #52331: Consider using more precise browser versions for `browserslist`.

Open Floor

@sergeybiryukov reminded the group that Beta and RC releases used to come with a haiku. He wrote one for the 50,000th commit and would like Core to restart the tradition.

@metalandcoffee volunteered to do a haiku for Beta 1 and closed the chat.

#5-6-1, #5-7, #core, #dev-chat, #summaries, #summary

DevChat Meeting Summary: January 7, 2021

@thewebprincess and @webcommsat led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC.

Thanks to @nalininonstopnewsuk and @webcommsat for the notes.
Slack archive for the 20:00 UTC meeting.

Announcements

  1. WordPress 5.7 news

2. Workshop submissions and testing calls

  • Full Site editing update
  • Learn WordPress
    • Got a dev workshop, or thinking of designing one? Submit it to Learn WordPress. Here’s a great example on using tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., that is already there: https://learn.wordpress.org/workshops/.
    • Follow and share promotions for #LearnWP and Meetups on social media too @WordCamp, @WordPressEvents and LinkedIn.

3. Monthly and weekly updates/ bulletins

Updates from the Component Maintainers and Focus Leads

Component maintainers do really important work. More about components at https://make.wordpress.org/core/components/

  • Update from @sergey:
    • Build/Test Tools – These change the frequency of code coverage reporting. A change was made in [49931] to display a relatively accurate code coverage data at https://codecov.io/gh/WordPress/wordpress-develop on any given day of the week.
    • Some other changes include updating several NPM packages and simplifying Composer package caching
    • I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Date/Time, Permalinks: No major news this week.
  • Update from @sarahricker on accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)
    • several Accessibility Team members volunteered to stay up to date with accessibility needs for each component/focus
    • if your component doesn’t connect with an Accessibility member soon, let the team know.

Open Floor

  • Update from @Sergey on 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/ 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/ or can be cost-based plugin from a third-party:
    • After almost a month since WordPress 5.6, for some reason the Gutenberg plugin still shows “Tested up to: 5.5.3” in the Plugin Directory and “Untested with your version of WordPress” when searching from a WordPress 5.6 adminadmin (and super admin), leading to search results that are not exactly great: https://cldup.com/nmU8Bq64U1.png
    • Note how every other plugin is listed as “compatible with your version of WordPress…”, but Gutenberg is “untested”.
    • Could we have an established process for updating the “Tested up to” version for Gutenberg? Boosting exact slug/name matches for plugin search was previously discussed in #meta3327 and some other 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. tickets. Apparently it’s not something that can or should be done at this time, however making sure that the “Tested up to” version is accurate should give us better search results. Ticket #3327: Searching with exact plugin name has it on page 3 of results
  • Promoting guidance for updating plugins to related WordPress versions
    • @webcommsat: Marketing has heard from Meetups and contributor events on intro talks on plugins development or basic talks on installing plugins: uncertainty about how plugins show they update to the current version. Potential to further promote guidance and advice.
    • @audrasjb recommended the Plugin development FAQ

Goals for 2021

Tickets requesting feedback

#5-7#devchat

#5-7, #core, #dev-chat, #summaries, #summary

Dev Chat Summary – 2 December 2020

The meeting was facilitated by @peterwilsoncc and @thewebprincess while @mikeschroder and @johnbillion took notes. Full meeting transcript on Slack. Both groups followed this pre-prepared agenda.

Announcements

Highlighted Posts

  • A Week in Core – November 23, 2020
  • What’s next in Gutenberg? The monthly report is out
  • Discussion: Update the updater
  • Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are continue to be updated ready for final release, here’s the latest dev-notes.
  • Release cycle discussion post – we need your feedback!
  • WP Notify project review

Component maintainers and focus leads

@peterwilsoncc reminded everyone that these components are in need of maintainers:

If you’re wondering what being a maintainer involves, @markparnell linked this guide from @francina.

Open Floor

@noisysocks requested review on #51612, which aims to make the  render_block_data, pre_render_block and render_block_context filters run on nested blocks. The PR with the latest approach can be found here.

The 2000 UTC group discussed #51913 and #51918 which led into a general discussion about the level of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support in 5.6 and how to communicate it. @marybaum asked for clarity to ensure all the marketing messaging is accurate.

The current consensus is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is “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.-compatible”, which means 5.6 works on its own with PHP 8, but that any given site may not work due to the plugins and themes in use and that more defensive programming is needed in core.

Next Dev Chat Meeting

The next meetings will take place on December 9, 2020 at 0500UTC and December 9, 2020 at 2000UTC in the #core 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/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

Apologies

Apologies from @johnbillion for the late posting of this summary. The post sat in draft until today when I was reminded of it.

Onwards!

#5-6, #5-7, #core, #dev-chat, #summaries, #summary

WordPress 5.6 RC 5

A fifth and final 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). for the WordPress 5.6 release has been packaged to mark the code freeze before release tomorrow, December 8. The following changes have been made since RC 4:

  • Twenty Twenty One: Fix nesting of main element ([49760] for #51944)
  • Application Passwords: Ensure detection accounts for multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site ([49765] for #51939)
  • Bundled Themes: Bump all versions for release ([49766] for #51919)

You can download the package here or use 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. 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/ or can be cost-based plugin from a third-party to update your sites. Happy testing, and see you all tomorrow in #core for the WordPress 5.6 release party!

#5-6

Media Meeting Recap – December 03, 2020

The following is a summary of the weekly Media component meeting that occurred on Thursday, November 3, 2020 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @sergeybiryukov, @joedolson, @hellofromtonya, @joel-yoder, @mista-flo, @aristath, @alexdeborba

Media Focus for 5.7

The focus for 5.7 was discussed and it was mentioned that there were many outstanding accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues that should be considered. It was agreed these should be moved into the scope of the release.

#50105: Remove infinite scrolling behavior from the Media grid

#50273: Media modal uses incorrect ‘checkbox’ role for list items

#47120: Media modals: Upload errors and field information are not associated with their control

#39004: Alt attributes should be searchable in media library

There has been a bit of buzz in the Media 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/. channel around a desire for more modern media formats to be considered as a focus. @azaozz recommended prior to the meeting that the following is considered when modern image formats are considered for 5.7.

A Media Focus Lead for 5.7 would be good if everybody here thinks we’ll manage to add support for (at least) .webp . Currently this is still at the “exploratory” stage. Main questions that needs solid answers:

How to resize WebP images?

How to detect browsers that don’t support WebP and serve fallback images?

Would WP expect the users to upload WebP images or would it convert JPEGs, PNGs and GIFs to WebP?

Seems that ideally WP will convert uploaded images to WebP and serve them when the site visitor’s browser supports them. The originally uploaded images would serve as fallback. Determining browser support would be best by “Server-side content negotiation via Accept headers”. Replacing <img> with <picture> on the fly would bring a lot of side effects/compat problems. Frankly not sure if that would be ready by the cut-off time of early to mid February, even if work starts right now  On the other hand, this needs to be done, 5.7 or not.

@azaozz

After a bit of discussion from attendees, it was generally agreed that for modern media formats there is still discovery work that needs to happen, a proposal to scope the work, and an outline of risks and blockers. The questions asked by @azaozz above are a good starting point in thinking this through.

@joedolson asked “Is there any reason modern image types can’t be staged across multiple releases? E.g., add support for uploading & inserting modern image types, and expand usage later? There’s nothing about adding WebP and SVG that requires them to be globally used; just made available. The bigger problems seem to be in what happens if you start auto-switching existing images between img/picture, etc.”

We’ll leave these these notes on 5.7 with an invitation to comment below about further considerations.

Time of Meeting

For frequent attendees it was determined that the current time of 15:00 UTC is currently working for most people’s schedules. If there are any thoughts on this time, feel free to comment below!

Props @antpb for proofreading and final review.

#core, #media, #summary