Twenty Twenty-One Test Scrub

As part of the 5.6 release, we’ll be hosting a Twenty Twenty-One focused test scrub today Friday, October 30, 2020, 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/..

What we will test

1. Image 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.https://github.com/WordPress/twentytwentyone/issues/737 – to test this issue, you need WP 5.6 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. 2 + latest version (trunk) of the theme
2. Dark-mode toggle: https://github.com/WordPress/twentytwentyone-dark-mode/issues/1#issuecomment-718679339 – to test this issue, you need WP 5.6 Beta 2 + latest version (trunk) of the theme + dark mode toggle plugin
3. 2 untested blocks > Group and column https://github.com/WordPress/twentytwentyone/issues/72

How we will test

  • We will go through each item as a group.
  • We will create a thread in Slack for each items where you can post the results. This will make it easier to reply in the existing issues or create new ones.

See you later!

#5-6, #bug-scrub, #test, #twenty-twenty-one

Dev Chat Agenda: October 28th 2020:

Here is the #agenda for this week’s meetings happening at:
Wednesday, 28 October 2020, 0500UTC and Wednesday, 28 October 2020, 2000UTC .

  • Announcements –
    • 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. 2 of 5.6 released – please test and review and bring any issues/bugs to chat to discuss
    • WP 5.5.2 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. planned for Thursday, 29 October 2020 1700UTC details here
  • Highlighted blogblog (versus network, site) posts
  • Calls from component maintainers and/or focus leads
  • Open Floor
    If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 28 October 2020, 05:00UTC and Wednesday, 28 October 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#5-6, #agenda

Widgets Screen Not Shipping in 5.6

The Widgets Screen project was pencilled in for 5.6, but as of 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, work on its major features was not complete, so Release LeadRelease Lead The community member ultimately responsible for the Release. @chanthaboune, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead @helen, Editor Tech Lead @isabel_brison and some of the contributors working actively on the project — @noisysocks, @talldan and @kevin940726 — decided to exclude it from 5.6. Thank you to everyone who tested and gave feedback as it helped inform this decision! 

The Reasoning

Making the Customizer work with the block editor is a challenging process, and one that needs  substantial and thoughtful work to make sure that we deliver the best possible user experience. At the current stage of this project a bulk of that work is done, but more focused testing revealed notable concerns for overall usability (including customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. interactions, some confusions between 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. & legacy widgets, and UXUX User experience disparities between the old and new screens). You can read more in the ticket.

Next Steps

We will continue working on the Widgets screen, and will keep the new screen as the default option when using the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 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 encourage more feedback.  At the top of the year, we’ll explore where this fits in the larger roadmap for future releases. For those looking to get involved until then, check out the options below: 

  • It’s been tentatively added to the WP5.7 milestone, with an early 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.) so that it comes up in scrubs as quickly as possible.
  • If you’re interested in following the status of the project, you can find the top priority issues and current focuses on the Widgets Editor project board in GitHub
  • If you can help with development, we encourage you to attend or review the weekly triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions in the #core Slack channel on Wednesdays at 7am UTC.
  • If you can help with testing, please feel free to leave comments on the Call for Testing for us to review or to open issues directly in GitHub. In particular, we’d love to hear from plugin and theme authors. 

Thanks in advance for everyone’s help making sure that this key element is a success!

#5-6, #5-7

Dev Chat Summary – 21 October 2020

This post summarizes this week’s meetings happening on Wednesday, October 21, 2020, 07:00 AM GMT+2 and Wednesday, October 21, 2020, 10:00 PM GMT+2 on the agenda.

0500 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat

0500 Full meeting transcript 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://wordpress.slack.com/archives/C02RQBWTW/p1599022834165200

@peterwilsoncc facilitated the meeting and took notes.

2000 core devchat

The meeting was facilitated by @laurora while @thelmachido took notes. Full meeting transcript on slack

Both groups followed this agenda.

First item: celebrating the first beta release of WordPress 5.6 on October 20! Please download 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. version, experiment with it on a test installation (not a live site!) and share any bugs you find or issues that come up.

Announcements

@annezazu announced the Widgets Screen won’t land in 5.6. A Make Core post is coming soon that will discuss where the feature is and what the next steps will be. And though the feature isn’t ready for the current release, it is still on the roadmap, and the team points out they still need feedback on the current work. You can give them that feedback, or share any other thoughts, here or on GitHub.

Highlighted Posts

Introducing Github actions for automated testing.

Please check it out! Your contributions are welcome.

Component Updates

PHP 8 call for testing

@sergeybiryukov highlighted the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 call for testing.

Build/Test Tools

Again, 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 running automated tests. See this post and this ticket for more.

@whyisjake is looking at a 5.5.2 release on Tuesday, October 27 or Thursday. October 29. He hopes to run a scrub tomorrow and then put the release docs together over the weekend.

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)

With the Beta 1 released, the team plans to switch gears to accessibility: namely, to review and package the Accessibility Statement feature 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. @jonnyvaughan and Alice Williams, who have begun coding the feature, would love some feedback and testing. Interested? Check out this GitHub repo.

Media

@mikeschroder asked for testing on #42663, which landed on October 20. He’s especially interested in your help if you write plugins that use stream wrappers.

He has two priorities:

  1. Make sure existing stream implementations still work.
  2. How hard is it to integrate those implementations with this new one?

Look for a dev notedev 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. from Mike as we get closer to final release. slack

Open Floor

@garrett-eclipse opened #51584 to ask if anyone else had hit the problem. After some discussion, the group concluded it is reproducible but doesn’t appear to be a 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. in WP 5.6 slack

@garrett-eclipse shared that he’s been wondering if WP notices should be active or passive. He has been leaning towards the convention that Google has and was wondering if he can add that to the handbook? @pbiron mentioned that US English spelling is mentioned in the handbook. Follow the conversation here slack.

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 28, 2020, 07:00 AM GMT+2 and Wednesday, October 28, 2020, 10:00 PM GMT+2 in the #core Slack 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. 

#5-6, #devchat

Dev Chat Agenda: October 21st 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday, 21 October 2020, 0500UTC and Wednesday, 21 October 2020, 2000UTC .

Bit of a late entry for agenda posts, apologies for that, it’s been a hectic couple of days… can you say 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?!! We’ll no doubt talk about that, but please also share any items you’d like to include in the comments below.

  • Announcements – let’s celebrate the release of Beta 1 of 5.6
  • Highlighted blogblog (versus network, site) posts

No other current posts to review. But please test and review the beta version and bring any issues/bugs to chat to discuss.

  • Calls from component maintainers and/or focus leads
  • Open Floor: If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 21 October 2020, 05:00UTC and Wednesday, 21 October 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#5-6

Introducing GitHub Actions for Automated Testing

As of [49162], CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is now running automated tests using 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 as a runner, in addition to the existing Travis CI and Appveyor runs. This post is to publicize the change, document the reasoning, communicate next steps, and share how people contributing to WordPress Core will benefit.

GitHub Actions allows us to automate software workflows directly in GitHub, triggered by GitHub events. By switching, we are able to take advantage of a unified interface, inline annotations for linting issues in pull requests, the broader open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. ecosystem building and using Actions including existing work in Gutenberg, and free availability for public repositories. Note that private repositories do use the monthly bucket of included minutes.

For contributors, this continues to refine the experience of working on Trac tickets using GitHub pull requests, most notably by showing linting errors inline in the diff view of the PR (known as annotations). This also consolidates external tooling into one place. If you have not already, please take a moment to associate your GitHub account with your WordPress.org profile.

Screenshot of inline annotation examples

These 6 workflows cover all current testing and analysis performed in Travis CI and Appveyor:

There is also an additional 7th workflow that is meant to leave a welcome message when it’s the contributor’s first pull request, letting them know how we use GitHub pull requests and how to link them to a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.. There appears to be an issue concerning permissioning when PRs are sent from forks, so this is pending.

Currently, Travis CI and Appveyor will continue to run for a transition period (ending TBD) to allow for any issues to be ironed out, and so that real-world usage data can be collected. So far, even in early testing, runs appear to be completing more quickly and with fewer/no false negatives, e.g. when Travis CI does not see the commit in the mirror yet. @desrosj will be collating run data in a spreadsheet, including but not limited to: overall build time, run time comparison (where 1:1 comparisons can be made), and frequency of false negatives.

Known next steps

  • Add and configure 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/. notifications. In addition to sending the results of the whole build of a core commit into #core, we may also want to consider a firehose channel for PRs.
  • Move to GitHub badges for build status indicators – note that these are per-workflow, which is different from the single badge for the entire Travis build for a given commit. However, GitHub does report an overall status for a commit/PR, so we may be able to use that information as well.
  • Report test results to the Host Test Results page.
  • Switch to ESLint from JSHint, as the latter does not appear to easily support inline annotations, and the former is in broader usage including in core for docs, 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/ and many community projects. See #31823 for more – volunteers very much appreciated here.
  • Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the workflow files to actively maintained older branches.

As always, please report any issues you are seeing with our GitHub Actions, as well as further ideas for use you may have. Major thanks to @desrosj for all the heavy lifting he’s done in just a couple of weeks, and to @ocean90 and @ayeshrajans for their help along the way.

#5-6, #build-tools, #unit-tests

Dev Chat Summary 14th October 2020

Hello Friends! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat on Wednesday, October 15th, 2020, 05:00 UTC and Wednesday, October 15th , 2020, 20:00 UTC, following this agenda .

05:00 UTC core dev chat @thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.
20:00 UTC core dev chat @thelmachido facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here.

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/13/dev-chat-agenda-october-14th/

Announcements

  • APAC based core committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., @peterwilsoncc has taken up a role that will allow him to contribute to core 4 days a week 🎉
  • A group is gathering around issues that can be moved to a minor release to clear the path for 5.6 and address issues like removing the embed blocks for FB an Instagram due to their withdrawal of support. If you can help, here’s where to dig in https://core.trac.wordpress.org/tickets/minor @whyisjake will be organizing the release, so reach out if you want to get involved.

No Highlighted Blogblog (versus network, site) posts this week

Updates from Component Maintainers/Focus Leads

Open Floor

  • @mikeschroder observed some failing tests for some hosts and the 0500 UTC crew dug in to find the cause in a package update – resolution to add an issue to the board to be included for the next 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/ release.
  • @isabel_brison threw out that if anyone was keen to work on or review editor-related stuff, the 5.6 project board has a few things to pick up in To do and Needs Review columns :smile:
  • The state of PHP8 support in core generated a fair amount of discussion. Rather than summarize here, please review the archive of the conversation in Slack for all the detail. Major takeaways are the 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 in progress in relation to communication around the significant number of breaking changes – Helen called for a deliberate effort towards outreach of this change which has extensive discussion to follow. Furthermore @omarreiss suggests declaring WP incompatible with PHP8 with a useful perspective from @jrf in response. Lots to dig in there, and there will be marketing and outreach efforts to ensure widespread awareness.
  • @justinahinon opened a discussion with a suggestion regarding pairing existing contributors with new ones to build connection and support newbies.
  • @helen asked for a rundown on significant issues to complete before 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 is released,
    • Major Core auto-updates opt-in UIUI User interface
    • Twenty Twenty-One
    • Widgets as Blocks
    • JQuery 3.5x
    • Issues on this list

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 15 2020, 05:00 UTC and Wednesday, October 14, 2020, 20:00 UTC 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.

Thanks to @francina for proofreading this post.

#5-6, #summaries, #summary

Dev Note Scrub for WordPress 5.6

With 5.6 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 approaching fast, there will be a Dev Notedev 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. 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 10/19/2020 19:00 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/..

The objectives are:

  • Recruit potential dev-note writers
  • Review tickets that need 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.

This scrub will focus on 5.6 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets that have the needs-dev-note keyword. Here’s the report: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~needs-dev-note&milestone=5.6&col=id&col=summary&col=status&col=milestone&col=keywords&col=owner&col=type&col=priority&col=component&col=changetime&order=changetime

What is a dev note?

A Developer note (or “dev note” for short) is a blogblog (versus network, site) post on the Making WordPress Core blog that details a technical change in an upcoming release and what developers need to know about that change.

Writing developer notes CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Handbook

Come join us.

This post was proofread by @hellofromtonya and reviewed by @davidbaumwald

#5-6, #bug-scrub, #dev-notes

Dev Chat Agenda: October 14th…

Dev Chat Agenda: October 14th 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday, 14th October 2020, 0500UTC and Wednesday, 14th October 2020, 2000UTC .

Please share any items you’d like to include in the comments below.
* Announcements
* Highlighted blogblog (versus network, site) posts – (None at the time of posting this agenda)
* Calls from component maintainers and/or focus leads
* Open Floor
If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 14th October 2020, 05:00UTC and Wednesday, 14th October 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#agenda #5-6

Dev Chat Summary 8th October 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, October 7th, 2020, 05:00 UTC and Wednesday, October 7th , 2020, 20:00 UTC, following this agenda .

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here .
20:00 UTC core dev chat
@laurora facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here .

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/06/dev-chat-agenda-weds-7th-october-2020/

Announcements

No announcements today!

Highlighted Posts

  • https://make.wordpress.org/core/2020/10/01/whats-next-in-gutenberg-october/ No action needed, but posted for awareness as there are notes for 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. or 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 devs and in invite for those interested in contributing.
  • Requests for comments on Starter Content https://make.wordpress.org/core/2020/10/06/revisiting-starter-content-on-org-and-beyond/ – which is a request for comment.
  • Progress update on https://make.wordpress.org/core/2020/10/06/update-wordpress-5-6-release-progress/. No action required though a request for a graphic depiction of what the Full Site Editing simple, routine user flows was discussed. This will help give people a sense of how it’s likely to work when it does come into core as it’s currently hard to visualise something we’ve not seen before.

Updates from Component Maintainers/Focus Leads

  • Build/Test Tools, General: Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support:
    • The PHP 8 Docker image has been updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x
    • A new NPM task has been added to use the Composer-installed version of PHPUnit
    • * There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
    • * Next steps: More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. A call for testing was published earlier this week: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/
      Question was asked: Does PHP8 support need more people involved? A: Follow the issues here PHP8 Tag in trac
  • 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.
  • Site Health has had some attention in the past week to go over 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.-refreshes and tickets
  • External Libraries: jQuery update has some progress too #r49101 has updated jQuery and jQuery UIUI User interface. Please test!
  • Upgrade/Install: our main ticketticket Created for both bug reports and feature development on the bug tracker. ( 50907 ) is still in progress.

Open Floor

  • The Marcomms team noted that they’re inviting feedback in relation to the About Page for 5.6 in thisGoogle form feedback is are also welcome via tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. but this form will help make it more accessible to the wider community who might not be familiar with trac and its processes.
  • It was observed that the titles for the dev chat entries in the calendar weren’t updated with the UTC specific timings so @peterwilsoncc updated them to Core Development Weekly Chat (0500 UTC) and Core Development Weekly Chat (2000 UTC)
  • #40351 (Term post re-counts scale poorly, are common and difficult to avoid) – WordPress Trac which is slated for 5.6 has a patch, but the question was asked whether there’s enough time to test properly before adding to the release, after discussion, the plan is for further testing this week, if nothing breaks it will be added to the release.
  • Discussion then went on to explore options for dummy content for testing andthe contingent posted numerous options according to individual preferences to answer the inquirer.
  • #50658 was highlighted for review: ‘has patch. Tested. Has screenshots. Missed wp5.5 deadline and tagged for 5.6. Action: pings sent to the component maintainers for review
  • Ticket https://meta.trac.wordpress.org/ticket/5463 was highlighted for feedback in relation expediting updating process for component and focus teams. Please comment on that ticket if you have feedback.
  • https://core.trac.wordpress.org/ticket/50907 needs more eyes on it and feedback added to the ticket.
  • The Yoast team have put together a short term team to focus on Twenty Twenty-One development, they’ve created a project board which you can follow here to track progress of issues
  • Reminder: next test scrub on Friday October 9th 13:30 UTC
  • Requests for testing: of https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/ and

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 20:00 UTC 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.

Props to @francina for the proofread.

#5-6, #summary