Tag Archives: summary

David Ryan 10:08 pm on November 3, 2021
Tags: , , , summary   

Dev Chat Summary: November 3, 2021

@francina led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <dev-chat> in #core on Making 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/..

Notable news and blogblog (versus network, site) posts

Component Team Updates

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

  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 compatibility fixes #53635
  • PHP Coding Standards fixes for 5.9 #53359
  • Removed role="navigation" from Core & Bundled Themes #54054
  • Permalinks: sanitize non-visible characters. #47912

@francina and @audrasjb highlighted the call for new Core Team reps for the next calendar year, emphasized reps do not need to be experienced contributors or developers to fill the role and outlined some of the main tasks.

Also, contributors are still needed for the WordPress 5.9 Release Squad (details on the responsibilities).

Build/Test Tools

  • Preliminary work on 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 in Core. #49606
  • Continuing work on end-to-end (e2e) tests in Core. #49507
  • Add missing @covers to PHPUnit tests. #39265
  • Improving Slack Notifications via 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. #53363

Date/Time

  • Improved inline documentation #53399

About/Help

  • Next 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 is Monday, November 8 at 19:00 UTC, following three prior scrubs for 5.9.

Editor

  • 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/ 11.9 (the last release going into WordPress 5.9) has an RC cutoff of November 5.

Open Floor

  • @hellofromtonya called out the WordPress 5.9 Feature Freeze is November 9. Work then shifts to defect tickets until the 5.9 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 target date of November 16.
  • @francina brought up a Gutenberg PR (36168) to remove the 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. menu item when 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. Themes are active. @johnbillion raised #54370 in relation to this change. If you build 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 extends the Customizer, please test with this change!

Watch For

  • WordPress 5.8.2 is currently in RC’s. 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. expected on November 10.
  • WordPress 5.9 Feature Freeze is November 9.
  • Our next Weekly Developer Chat is Wednesday, November 10 at 20:00 UTC

#5-8-2, #5-9, #dev-chat, #summary

Justin Ahinon 3:28 pm on November 3, 2021
Tags: , , , summary   

Performance team meeting summary – November, 2 2021

@justinahinon led the meeting. You can also read the Slack logs.

Performance team resources/reading materials

If this is the first time you are hearing about the WordPress performance team, here are some links to get you started:

Defining focus areas and working groups

Since the initial post on the proposal to create the team, there have been additional ideas on what it should work on. We need a bit of prioritization. Of course all performance work is important, and all contributions are welcome, as always.

To have a guideline for the next steps, the attendees decided to choose in the spreadsheet mentioned above from the aspects that have the highest number of interested contributors. These topics will be organized in working groups, that will be discussed during the weekly meetings.

Here are the working groups:

  • Images: Serving images in good quality but as small as possible
  • 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/.: Optimizing JavaScript orchestration
  • Site Health: Providing the user with data to understand performance
  • Measurement: Compiling data and analysis, and reporting on performance

To make sure we are making steady progress, we asked for at least one volunteer per working group to commit to attending weekly meetings to give updates on what is being done, and possibly how other contributors could help. Here’s the thread on Slack where you can express your interest in doing so.

Next steps for this team

The next steps for the team and the working groups are the following:

  1. Define the logistics for each group (tracking, POCs etc.)
  2. Kickoff meeting for each 4 area

If you are interested in exploring or helping with one of these, please feel free to add their .org username in the Focus Area speadsheet.

Open Floor

Several ideas were brought up during the meeting, about the organization of the team, potential tools or ideas for exploration. Here are some of them:

About tooling/documentation/information about performance and monitoring

About some work that is already being done for performance

@audrasjb is doing some work for the Site Health focus. Audras is working on a feature plugin on Benchmarks in Site Health, number of CSSCSS Cascading Style Sheets./JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. assets loaded.

Thanks @francina and @tweetythierry for the peer review

#meeting, #performance, #performance-chat, #summary

Andrei Draganescu 3:05 pm on November 1, 2021
Tags: , , , , summary   

Editor chat summary: 27 October, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, October 27 2021, 04:00 PM GMT+1. in Slack. Moderated by @andraganescu.

General updates

Future agendas we should drop the “What’s Next in ..” reminder link as the Go/No Go post supersedes the “What’s Next”.

@juanmaguitar asked who are the Proposed WordPress 5.9 Leads and got directed to the early squad list here that should be published soon.

@noisysocks mentioned Gutenberg 11.9 is the last plugin release which will make its way into WP 5.9. It will be “cut” on November 3 which is very soon.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Global Styling

@jorgefilipecosta provided an update:

  • A PR proposing the new color palette editor and a PR that makes multiple color palettes from different sources available to users were proposed PR 35783, PR 35783.
  • The new global styles 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/. endpoints are also in progress PR 35801, PR 35985, and at least the endpoint for user styles should be merged in the next hours.
  • The new design is based on progressive disclosure UIUI User interface where all the options are not visible right away that is based on using the new tools panel on the multiple 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. supports that exist, and that work is also in progress for colors and borders PR 33743, PR 34027. 

Patterns

  • @ntsekouras explained that while the  patterns tracking issue suggested to implement a way for allowing themes to surface specific patterns from the pattern directory, in reality development is tightly coupled with the pattern directory and the current ‘closed’ submission system, so more exploration needs to happen.

Navigation Block & Navigation Editor

@getdave provided an update:

Mobile Team

@hypest provided an update:

Shipped

  • Rolled out in-editor Help screen and new-block Inserter Badge to all users.

Fixes

  • Pin Node to v14 on CI to match 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/ web’s CI.
  • Autosave issue in the Unsupported Block Editor.
  • iOSiOS The operating system used on iPhones and iPads. Safe Areas issue in the in-editor Help screen.
  • Fixed a loading glitch in the embed blocks.

In Progress

  • Adding more tests for the Embed block.
  • GSS Font size, line height, colors.

Task Coordination

@mamaduka

  • Fixed 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 was causing post editor to crash when switching between preview types.
  • URL Details endpoint now will check og:description when searching for site description.
  • Fixed (waiting for review) the bug for Classic block. It was copying content to other blocks during the “Select all” action.

@jorgefilipecosta

  • Reviewed and helped the work to fix the background text higlings migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. that was affecting websites in production using the 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 https://github.com/WordPress/gutenberg/pull/35516.
  • Implemented the new color palette editor.
  • Updated color and gradient components to show colors from all the origins.
  • Submitted some smaller fixes and enhancements.
  • Reviewed the global styles endpoint.
  • Multiple smaller PR reviews.

@bph

  • Tomorrow Live Q & A on Converting classic Widget to blocks w/ Buddy Press team @imath  @vapvarun and @dcavins  – Join us and/or share in your networknetwork (versus site, blog). It will be streamed to YouTube as well. (by the time meeting notes come out we might have a recording on YouTube. )
  • Prep and recording of Gutenberg Changelog episode 54 – Gutenberg 11.8 and more. w/ @gziolo
  • Developer Hours to start mid November. Coordination work ongoing.
  • Preliminary prep for WordPress 5.9 documentation

@getdave

@ajlende

@annezazu

  • accepted test co-lead for 5.9 along with helping with user docs
  • working on the next round of FSE answers,
  • working on figuring out next call for testing,
  • doing some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. + testing!

@colorful-tones

  • I’m looking for some guidance on Global Styles: Form elements. I’m looking to dive in today and get a PR going, but want to make sure I have scope and scale in mind for adding any features.

Open Floor

@cbravobernal asked about issues because of getting block attributes with style and class together in a string and pointed to the trac issue.

@overclokk raised an issue detailing a proposal to remove block-templates and block-templates-parts directories for FSE – Full site editing

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Jb Audras 10:00 pm on October 27, 2021
Tags: , , , summary   

Dev chat summary – October 27, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

After 1.5 year, @francina and @audrasjb decided to pass the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Representative baton for 2022. Everyone can nominate the people they think are best suited to be our new Core team reps, just comment in the above post.

Upcoming releases updates

Next 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.: WP 5.8.2

@desrosj confirmed WP 5.8.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). is still planned for Tuesday November 2, with a few tickets including #54207 which has been quite a pain for many, so fixing it sooner rather than later is best.

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.: WP 5.9

First the Release Squad for WordPress 5.9 was published. If anyone is interested in volunteering for one of the roles needing more help, please comment on that post. If anyone has any questions about the release squad roles, some answers are available in the Core team handbook.

@audrasjb and @chaion07 published the 5.9 Bug scrub schedule.

Next scrubs are scheduled on Thursday October 28, 2021 at 20:00 UTC and on Friday October 29, 2021 at 06:00 UTC.

Please note that anyone can run 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. Checkout the Leading Bug Scrubs section in the Core handbook.

Also, a WordPress 5.9 Editor Update (26 October) was published.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

The 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 workflow was modified to be a reusable one. See changeset [51921] and some follow-up changes on ticketticket Created for both bug reports and feature development on the bug tracker. #53363.

General – @sergeybiryukov

Work has continued on various coding standards fixes in core. See tickets #53359, #54177, #54279, #54295 for more details.

Help/About – @marybaum

Two tickets are getting closer to commit but not completely there. Copy reviews are done, the component maintainers have new patches. Should be able to commit both by next Monday’s component scrub.

Open Floor

@craigfrancis wanted to discuss #54042, as I’d like to make the IN() operator easier/safer, and likewise with quoting table/field identifiers. Given the amount of information shared in the PR, @audrasjb moved this ticket to 5.9, but it will need a deep review as soon as possible to be committed ahead of the feature freeze which is the target for such enhancements.

@marybaum asked if there is still feature freeze a week or so ahead 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. Feature freeze is scheduled on November 9th, and Beta 1 is on the 16th.

@afragen shared a message of @peterwilsoncc from the #core-auto-updates Slack channel. The Upgrade/Install team will meet in this channel on next Tuesday to discuss a proposal concerning 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 Dependencies feature.

#5-8-x, #5-9, #dev-chat, #summary

Dan Farrow 9:20 pm on October 27, 2021
Tags: , summary   

CSS Chat Summary: 21 October 2021

The meeting took place here on Slack. @dryanpress facilitated and @danfarrow wrote up these notes.

The meeting was short but props are due to @dryanpress for finding a way to run it despite having no internet!

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Thanks everybody!

#core-css, #summary

Paal Joachim Romdahl 9:19 am on October 25, 2021
Tags: , , , , summary   

Editor chat summary: 20 October, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, October 20 2021, 04:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

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 releases

Gutenberg 11.8.0 RC Thanks to @vcanales for tackling the release.
What’s new in Gutenberg 11.7 release notes. Thanks to @zieladam for writing the notes and handling the release.

Highlights:

  • Navigation 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. and Navigation Editor Advances.
  • Global Styles and Full Site Editing improvements.
  • Columns Block for tweaking gaps and margins.
  • Link control – Create a page directly inside the link control.
  • A default alignment option – none.
  • + various other enhancements.

WordPress 5.9 Planning Roundup

Proposed WordPress 5.9 Schedule, scope, leads and how to help.

5.9 Priorities

Preliminary road to 5.9.

Full site editing Go/No-Go

WordPress 5.9 feature full site editing Go/No-Go.

Navigation Editor and Block

Summary: Navigation Editor and Block hallway hangout

What’s next in Gutenberg.

What’s next in Gutenberg: Mid-September.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Update from @noisysocks

Global Styling

Update from @jorgefilipecosta

Patterns

Patterns explorer in modal PR by @ntsekouras.
Exploring a modal system for selecting patterns.

Navigation Block & Navigation Editor

Update from @get_dave

  • The Nav Editor will not be included in WordPress 5.9 – this is because: changes to the block are required for the editor to be a success (see below). We need to allow sufficient time to test the editor before any 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. and allow for community feedback.
  • Following the Hallway Hangout a summary was posted. The outcome was:
  • In the short term, contributor efforts will switch to the Nav block in order to resolve some of the underlying architectural issues
  • Specifically separating the navigation’s presentation from its data in order to make navigations reusable. This serves both the Nav Editor project and the WordPress 5.9 release in general.
  • The Navigation Editor will ultimately focus on manipulating the data of a navigation which is why the above work is a prerequisite for the project’s success.
  • Work on the Nav Editor will resume after WordPress 5.9. We will continue to focus on backwards compatibility whilst looking ahead to the world of blocks.
  • It’s unlikely that we will pursue a new “Classic Menu” block. Rather focusing on the Navigation block (or its data).
  • To this end @talldan has two important Nav block PRs which everyone is encouraged to test and provide feedback on.
  • Link to the Github Navigation Block & Navigation Editor issue.

Mobile Team

Update from @mattchowning

  • Shipped:
    Trigger embed bottom sheet when an embeddable url is pasted into a paragraph block
    Add ability to customize the text and background color in the search block
  • Fixes
    Small fixes for embed block and help screen
    Improve automatic dimming of cover block
  • In Progress
    Adding more tests for the Embed block
    GSS Font size, line height, colors

Task Coordination

@santosguillamot

The main idea is to end up with a Comment Query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. similar to the existing Query Loop we have for posts. You can check out the scope of the project in its tracking issue. This has been the progress so far:

@mamaduka

@joen

  • Focused on bringing home the navigation block, and making a bunch of tiny PRs to shore up the numerous mostly small glitches.

@annezazu

@ntsekouras

@bph

  • Started plugin/theme outreach regarding Gallery Block Refactor 15 top plugins, responses 10, I’ll do a second attempt to reach the non-responsive. TY @Glen Davies
  •  I will connect with 12 more plugin developers this week, and tackle theme authors.
  • Awesome Live Q & A w/ Helen, Mark and Riad – Discussion “How we make building blocks easier.  Recording on YouTube
  • Developer Hours. We’ll start coordinating schedule and promotion next week.

@get_dave

@paaljoachim

Open Floor

@welcher

@priethor

  • WordPress 5.9 Feature Freeze is planned for November 9th. Last Gutenberg release to be included in 5.9 is 11.9 RC.
  • Check the WordPress 5.9 Must-Haves project board. Contributors are encouraged to add items and bugs that seem necessary to include in this major release.

@clorith


#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Dan Farrow 4:56 pm on October 21, 2021
Tags: , summary   

CSS Chat Summary: 14 October 2021

The meeting took place here on Slack. @wazeter facilitated and @danfarrow wrote up these notes.

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @wazeter shared the planning document and noted that we’re in the final stages of migrating existing colour properties to CSS custom-properties
  • @dryanpress is working on reducing the huge number of custom properties in customize-control.css, a process which has revealed hex values shared by multiple properties. These could effectively be replaced by additional theme properties
  • @wazeter noted that sometimes in larger files it’s better to avoid find-and-replacing colour values and instead to go through logical property groupings e.g. box-shadows, then background etc.
  • @wazeter shared a link to every-layout.dev which outlines an approach to CSS architecture which could be relevant to this project, and which demonstrates the need for a good set of default custom properties
  • This led to a conversation about the next steps, in particular the documentation and Table of Contents (TOC) which will accompany the custom-property roll-out

Thanks everybody!

#core-css, #summary

Jb Audras 9:41 pm on October 20, 2021
Tags: , , , summary,   

Dev chat summary – October 20, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Worth mentioning:

Thanks to the 30 contributors of the past week, including 7 new contributors! Kudos to the 5 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.

A Week in Core – October 18, 2021

Upcoming releases updates

Next 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.(s)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets. WP 5.8.2 RC is scheduled on Tuesday November 2, 2021. With a final release on Wednesday, November 10, 2021.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads 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. This channel is public and will be archived once 5.9 is released.

From @desrosj: If there is anything you’d like to see released prior to 5.9, please make sure to flag it and help bring the ticketticket Created for both bug reports and feature development on the bug tracker. to a resolution!

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.

First announcement, it’s a GO for the main 5.9 features: WordPress 5.9 Feature Go/No-Go | October 14, 2021 🎉

@audrasjb and @chaion07 published the 5.9 Bug scrub schedule.
Please note that anyone can run 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. Checkout Leading Bug Scrubs in the core handbook.

@chanthaboune added that a Release Squad will be announced soon.

Twenty Twenty-Two was introduced a couple week ago. As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this project.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

A readme file for end-to-end (e2e) tests was added to WordPress core. It provides instructions of how to run the tests locally and links to documentation. This should hopefully result in more contributors writing e2e tests. See ticket #53550 for more details.

General – @sergeybiryukov

Work has continued on various coding standards fixes in core. See tickets #54177, #54277, #54278, #54284 for more details. Thanks to @sabbirshouvo, a new contributor, for improving escaping in various parts of core!

Internationalization (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.) – @sergeybiryukov

Some Media Library 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. strings now have a context for better translations. See ticket #54238 for more details.

Help/About – @marybaum

Scrubs continue weekly, hosted by @marybaum and @webcommsat. Three tickets will wind up contributing to big changes long-term; a couple of tickets are minor markup changes, so they should be good to go this week.

This component will have another scrub scheduled on Monday October 25, 2021 at 19:00 UTC, focused on tickets slated for 5.9.

Open Floor

@audrasjb asked for an update concerning the new Performance team proposal. @chanthaboune: “There are a few questions that I’m synthesizing into a comment. Performance is, of course, an important thing for the WordPress project as a whole. There were some questions on implementation, though.”

@janthiel asked for a review of #53450. @audrasjb moved it for 5.9 consideration. This ticket will need dev-feedback and a technical review.

@costdev is working on the changes from assertEquals() to assertSame() in the test suite for 5.9 and the “Stage 1” pull request is ready for review: #53364.

@tobifjellner asked for a review of #54300. @audrasjb moved it for 5.9 consideration and added 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. proposal.

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two

Jb Audras 10:26 pm on October 13, 2021
Tags: , , , , summary,   

Dev chat summary – October 13, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

The proposal for a new Make/Performance team was well received by the meeting participants. Encouraging! Please add your feedback in the post comments.

Worth mentioning:

Thanks to the 30 contributors of the past week, including 3 new contributors! Kudos to the 5 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.

A Week in Core – October 11, 2021

Upcoming releases updates

Next 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.(s)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads 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. This channel is public and will be archived once 5.9 is released.

@sergeybiryukov proposed to also 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. changeset [51883] (which is milestoned to 5.8.2) to older branches.

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.

Concerning the next major release —WordPress 5.9— a planning roundup was published some weeks ago.

@kjellr introduced the new bundled theme on Make/Core last week. The first Twenty Twenty-Two meeting was hosted on October 11, in the #core-themes Slack channel.

As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this project.

Introducing Twenty Twenty-Two

The go/no go date for the main WP 5.9 features is October 14.

@audrasjb will run another 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 October 14, 2021 at 20:00 UTC.

Reminder: everyone is welcome to run a bug scrub on the #core Slack channel. If you are interested, please read this handbook post: Leading bug scrubs and get in touch with @audrasjb or @francina for details.

Component maintainers updates

Upgrade/Install – @sergeybiryukov @afragen

Work has continued on addressing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher timeouts or missing files during large 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 theme updates. A couple of solutions were implemented so far, but it looks like the issue might not be fully resolved yet. Any testing and feedback welcome! See ticketticket Created for both bug reports and feature development on the bug tracker. #54166 for more details.

Also, @afragen made a few updates to the new move_dir() function based on @sergeybiryukov’s comments.

Help/About – @marybaum

Help/About: the component had a scrub Monday and is following up with another on @audrasjb will run another bug scrub on Monday October 18, 2021 at 19:00 UTC. So far two tickets are ready for commit action.

The #core-auto-updates team is still looking on getting a consensus on which approach to proceed with for #22316. Two competing PRs are proposed (1547 and 1724), there is a need to decide what is the best approach.

Open Floor

@johnjamesjacoby raised ticket #38231 and asked for another pair of eyes. @costdev pointed out some possible enhancements in the unit tests provided by the ticket.

@webcommsat shared that the Marketing Team is exploring how to help the Test Team reach extenders with the message to update their test suites to bring them in line with the latest WordPress Core PHP Test Suites.Everyone is welcome to join the collaboration in this document, and they are looking specifically for items to be filled in on the table on page 4 to 6.

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two

Dan Farrow 8:46 pm on October 12, 2021
Tags: , summary   

CSS Chat Summary: 07 October 2021

The meeting took place here on Slack. Thanks to @dryanpress for stepping in to facilitate at the last minute! @danfarrow wrote up these notes.

Housekeeping

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @dryanpress reported that @circlecube has updated comments on his PRs and has been pinged about outstanding merge conflicts
  • @dryanpress is working on .customize-controls.css, continuing @robertg’s extensive work on this 3000 line file
  • @wazeter and @dryanpress reflected on the Custom Property project’s ongoing achievements, made possible by the many generous contributors
  • @dryanpress restated some points from last week’s meeting:
    • custom-properties.css needs organising and the addition of a table of contents
    • box-shadow declarations should be put into custom property
    • This is still the first-pass – there will be further consolidation of the custom-properties

Open Floor / CSS Link Share

Post-meeting chat!

Thanks everybody!

#core-css, #summary