Dan Farrow 1:44 pm on March 17, 2021
Tags: ,   

CSS Chat Summary: 11 March 2021

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

Housekeeping

  • @ryelle noted that daylight savings comes into effect in the US on March 13th and asked if we should change the meeting time
  • @danfarrow agreed that it would be good to move the meeting time but maybe not until UK daylight savings has come into effect at the end of the month, as otherwise the meeting would be at 11pm in the UK
  • We agreed that the next meeting should stay as 22:00 UTC and we can discuss the change then – if you have a preference please let us know!

Discussion: Ideas for custom property naming

  • @danfarrow shared his custom property naming for buttons mock-up which, with a little cheating, reduces the custom properties to --button-color,
    button-contrast-color and --button-active-color
  • @ryelle liked the use of the word contrast to clarify the intent of the custom property
  • @ryelle’s --color-$n approach received support from @audrasjb & @danfarrow, however it still has the issue of a lack of context. When defining the numbered colour values it’s not clear what the contrast relationships should be between them
  • We concluded by following up @notlaura’s idea from last week of having people mock-up another UIUI User interface component of their choice with custom properties. It would be great if people could bring their mock-ups to the March 25th meeting!

Project updates

  • There were no project updates this week

Open floor / CSSCSS Cascading Style Sheets. link share

  • @sabernhardt shared a link to ticketticket Created for both bug reports and feature development on the bug tracker. #52760: Color not 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) for AA which @ryelle offered to look at
  • @sabernhardt also asked for anyone with good flexbox knowledge to join the discussion on #28983: Adminadmin (and super admin) bar length or Admin bar on two line

With that our time was up. Thanks everyone!

#core-css, #summary

Jonathan Desrosiers 11:01 pm on March 16, 2021  

Trial run: Consistent minor release squad leaders for each major branch

Minor releases (X.Y.Z+1) are WordPress releases that fall between major releases (X.Y+1) providing 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, small, self contained enhancements, and security fixes when appropriate. Minor versions are released as necessary. The current cadence is one every 4-6 weeks.

Since WordPress 3.2, minor releases have been released (on average) every 5 weeks after another major or 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.. This cadence has increased slightly since WordPress 5.0 to an average of roughly every 4.5 weeks.

Pain points

With the minor release cycle, there are currently several pain points that make planning and executing difficult.

(Much) Shorter release cycle

The shorter release timelines for minor releases enable faster iteration on features included in major releases, and allows important bug fixes to be delivered to users faster. Which is great! However, it makes other parts of the release cycle, such as compiling a release team, much more difficult (this process can sometimes take up to 2 weeks).

The real work for a release does not fully commence until after a release team is assembled. This results in minor releases having even less time for actual work than they should (2-4 weeks instead of 4-6).

Unknown scope

While minor releases focus only on bug fixes and small, self contained enhancements, some have a smaller, more targeted scope aimed at a more specific area of the code base.

For example, if Feature A is included in the X.Y 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., the scope for the X.Y.1 minor release may be aimed at polishing the user experience of Feature A. It can sometimes take 1-2 weeks to determine whether a more targeted scope is required (this is dictated by the incoming support and ticketticket Created for both bug reports and feature development on the bug tracker. volume).

Contributor focus

Oftentimes, minor releases are organized and executed by contributors that are also working on tickets, tasks, and features for the next major release. This can lead to divided attention and focus spread out between too many items.

Additionally, when the date of an upcoming major release is nearing, it can cause a longer than usual gap when the attention of these contributors shifts fully to the next major release. For example, 5.4 was released nearly 15 weeks after 5.3.2. While this is the longest gap since 5.0, it’s not uncommon for a major release to be released 8-12 weeks after the last minor from the previous branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (the average since 5.0 is nearly 8 weeks).

Though as many contributors as possible should focus on testing the next major release, there should not be a huge gap. Having a small team focused solely on minor releases will hopefully help shrink that gap while allowing other contributors continue to focus on the next major release.

Security

Occasionally, a minor release will include fixes for security vulnerabilities. These releases happen under a few different conditions:

  • There are enough security fixes to push out a minor release solely containing security fixes.
  • There is a minor release already planned and the security team is able to have fixes for known issues prepared.

However, it’s difficult for the security team to plan and coordinate when minor releases will occur and, due to the issues mentioned above, know who to coordinate with.

Consistent minor release leads

For the upcoming 5.7.x releases, a release leadRelease Lead The community member ultimately responsible for the Release. and release deputy will be named for all 5.7.x releases, and will serve until 5.8 is released.

These two contributors will be responsible for:

  • Publishing timelines and plans for each minor release.
  • Executing these plans through release day.
  • Coordinating with the Security Team lead to improve the flow of fixes from the team to users.
  • Assembling and requesting help from other volunteers for each release as deemed necessary (docs, test, specific focus areas, etc.).

Ideally, one of these two contributors has a technical background (with the abilities to identify, confirm, test, and approve bug fixes and changes), and the other has a project manager or coordinator background (with the abilities to create release timelines, coordinate contributors, and help unblock efforts).

One additional (potentially optional) criteria would be that either the lead or deputy be a part of the previous major release’s squad, or be very familiar with the changes that were introduced in that major release. This would further increase the speed at which the minor releases are able to fix related bugs, as they are already “up to speed” on the changes.

In recent years, the gap between major releases has been, on average, 3 to 5 months. If necessary, contributors can 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.) in and out of the role should circumstances change and it becomes necessary.

The hope is that by eliminating the need to plan each and every minor release from scratch, the actual time contributors have to work on active bug fixing, triaging, testing, etc. will be increased, allowing minor releases to deliver fixes to users more quickly and effectively.

If this works and the decision is made to continue this practice into the 5.8.x releases, the next two contributors should be named prior to 5.8’s final release to ensure a smooth transition.

Volunteering

If this is something you are interested in and you anticipate having the bandwidth for the next 3-4 months, or if you will be available to help our for the 5.7.x minor releases in other ways (triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., documentation, etc.), please feel free to comment below!

And of course, questions and feedback are always welcome!

Props @chanthaboune, @jeffpaul, @cbringmann, and @davidbaumwald for peer reviewing.

Francesca Marano 10:05 pm on March 16, 2021
Tags: ,   

Dev Chat Agenda for March 17, 2021

Here is the agenda for this week’s meetings to occur at the following times: March 17, 2021 at 5:00 UTC and March 17, 2021 at 20:00 UTC.

Announcements

  • Last week WordPress 5.7 “Esperanza” was release, in case you missed it

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #dev-chat

Francesca Marano 7:37 pm on March 16, 2021
Tags: ,   

X-post: Proposal: A WordPress Project Contributor Handbook

X-comment from +make.wordpress.org/updates: Comment on Proposal: A WordPress Project Contributor Handbook

Kjell Reigstad 7:02 pm on March 16, 2021
Tags: ,   

X-post: Block-based Themes Meeting Agenda: Mar 17, 2021

X-post from +make.wordpress.org/themes: Block-based Themes Meeting Agenda: Mar 17, 2021

annezazu 12:38 am on March 16, 2021
Tags: , fse-outreach-program, ,   

High level feedback from the FSE Program (March 2021)

After a few months and a few rounds of testing for the Full Site Editing Outreach Program, this post summarizes the top pieces of feedback of the current experience to help inform ongoing efforts for an MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia. Keep in mind that this post is simply a snapshot in time and is inherently going to leave out aspects of the experience that haven’t been the subject of calls for testing yet, for example, Global Styles. If you want a more in-depth look at feedback across the testing calls and a full summary of all issues rather than a sampling, please review the summary posts. If you want to help give feedback, join the calls for testing or test whenever you’d like. 

Previewing content

Across both calls for testing, it quickly became clear that previewing changes is a workflow people rely upon and miss deeply in the current experience, whether it was a desire to preview changes to a template or to preview the entire site. A “Preview Site” option is currently under discussion, along with exploring a possible browsing mode allowing a user to browse around their site within the editor. 

Saving Process

While the saving experience was reliable technically and generally intuitive, it has left a lot to be desired and resulted in a fair bit of confusion around expected behavior. This is likely because multi-entity saving (saving multiple aspects at once) is a new WordPress concept and one that underpins every interaction in the Site Editor. Whether it was mentioning desired features, finding bugs, or confusion around how to accomplish a task, this proved to be a robust area of feedback. 

The distinction between editing the entire site vs. specific content

Similar to the saving process feedback, this is another area where features technically work but are difficult to distinguish across the experience. For example, one can edit a template directly, but it’s not always clear when one is editing a template or editing an item of content. Beyond just clarity in what one is editing, there needs to be the right amount of friction when switching between content that impacts the entire site vs. content on an individual post/page. This is an area of active iteration and exploration to get the right amount of friction in place, as you can see in open issues like this one around clarifying template vs. content editing, and this one around refining the experience of editing a template part in isolation.

Rethinking Width/Alignment

Currently, alignment in Full Site Editing works to optimize traditional themes that provide their own alignment styles. This approach has served the project well until this point, but it’s a key area to reconsider to ensure a true and reliable WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience. Thankfully, work is already underway in an important PR by @youknowriad to reimagine how this dynamic should allow for more control over alignments/widths when using the Site Editor. 

General Usability Improvements

As this work moves into a place of refinement, there are numerous enhancements to consider to improve overall usability of the Site Editor. This is a “catch-all” categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. but an important one nonetheless, as it will help the Site Editor experience move from functional to delightful. What follows is a sampling of items both to get a sense of the kinds of issues raised and the spread: 

Improving Placeholders

Placeholders for some of the newer blocks in the site editing experience prove to be both a powerful way to guide people and a point of confusion. This feedback mainly came into play with blocks like the Query Block (including the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. variations like Posts Lists), Social Icon Block, Featured Image Block, and the Navigation Block. Each currently gets users started in different ways. In the long run, it seems that users will benefit from a standardized, consistent way to interact with placeholder content across all blocks. This is particularly important when viewed through the context of editing a template where you might mostly see placeholder content. 

#core-editor, #fse-outreach-program, #full-site-editing, #gutenberg
Jb Audras 9:42 pm on March 15, 2021
Tags: ,   

A Week in Core – March 15, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between March 8 and March 15, 2021.

  • 12 commits
  • 17 contributors
  • 63 tickets created
  • 9 tickets reopened
  • 70 tickets closed

There has been a low activity this week, as WordPress 5.7 was released last week.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Administration

  • 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): Use a darker color for post dates in the Activity and Quick Draft dashboard widgets – #52760

Bundled Themes

  • Twenty Seventeen: Remove extra space around post editor – #52816

Site Health: Use a singular string in 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. if there is only one critical issue or recommendation – #52521
Docs: Correct unregister_block_style param for $block_name – #52795

Coding Standards

  • Consistently format opendir() calls in get_plugins() – #44250

Docs

Editor

  • Make 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. type aware of variations – #52688
  • Classic Editor: Make sure word count is hidden if 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/. is disabled – #52662

Help/About

  • Run image comparison script after all assets have loaded – #52758
  • Use absolute URLs for inline images on About pages – #52743
  • Correct the WebM video URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on About page – #52756

Props

Thanks to the 17 people who contributed to WordPress Core on Trac last week:

@audrasjb (4), @sabernhardt (3), @vladytimy (1), @jeremyfelt (1), @mihdan (1), @subrataemfluence (1), @TobiasBg (1), @Otshelnik-Fm (1), @gwwar (1), @timothyblynjacobs (1), @joyously (1), @kraftner (1), @hareesh-pillai (1), @Presskopp (1), @joseeyoast (1), @sergeybiryukov (1), and @mukesh27 (1).

Please join me to say welcome to our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@Otshelnik-Fm and @joseeyoast

Core committers: @sergeybiryukov (6), @ryelle (2), @peterwilsoncc (2), @davidbaumwald (1), and @gziolo (1).
Shout out to @davidbaumwald for his first commit 🌟

Please note: it only includes commits with proper props attribution.

#5-7, #week-in-core

Paal Joachim Romdahl 3:22 pm on March 15, 2021
Tags: , , ,   

Editor Chat Agenda: 17 March 2021

Facilitator and notetaker: @itsjusteileen

This is the agenda for the weekly editor chat scheduled for Wednesday, March 17, 2021, 03:00 PM GMT+1.

This meeting is held in the #core-editor channel in the 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/..

  • WordPress 5.7
  • 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.2
  • Monthly Plan for March 2021 and key project updates:
    • Global Styles.
    • 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 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. Editor.
    • Navigation block.
    • Full Site Editing.
  • Task Coordination.
  • Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Jonathan Bossenger 2:55 pm on March 15, 2021
Tags: ,   

WP Notify Office Hours Change

I’d like to suggest a shift in the weekly WP Notify Office Hours.

Due to a change in my personal life, I can no longer attend these office hours and successfully contribute.

I would therefore like to suggest that we move office hours to either Tuesdays at 14:00 UTC or Thursdays at 14:00 UTC.

I will leave the comments open until Monday, March 22, 2021, 18:00 UTC, at which time I will update this post with the final agreed upon change.

#feature-notifications, #meeting

Paal Joachim Romdahl 2:11 pm on March 15, 2021
Tags: , , ,   

Editor chat summary: 10 March, 2021

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

WordPress 5.7

WordPress 5.7 was released on the 9th of March.
Contains features such as various updates to the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor, from HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. to HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in a single click, new Robots APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., lazy-load iFrames and a lot more. A bit shout out to @noisysocks for his work as the technical Block Editor lead.

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.2

Download the RC version of Gutenberg 10.2.0.

Monthly Priorities

March monthly priorities. Along with Key Project updates. Thanks to @priethor!

Global Styles

Update from @nosolosw

Update from @hypest

  • Global Styles and mobile: Working on identifying tasks.

Block based 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. Editor.

  • Check out 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/. channel #feature-widgets-block-editor and various Widgets Screen issues 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/.

Navigation block.

Update from @mkaz

Navigation Editor screen.

Full Site Editing

Update by @youknowriad

  • Still focusing on making sure the experience is as WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. as possible without requiring implicit theme styles.
  • Landing a PR to normalize “figure” element styles.
  • Then another one to reset the WP-Adminadmin (and super admin) styles properly in the editor canvas to avoid CSSCSS Cascading Style Sheets. bleed as much as we can.
  • I’m still iterating on the alignments/widths PR of that work.

Task Cordination

@mkaz

  • Would like to bring focus to this PR. Draft: Pulling JavaScript to the frontend from a Core Block. The PR will require enqueuing 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/. on the front-end which has not been done from a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block before. The results of the PR can also help get an accordion block into Gutenberg. Associated merged PR should help enqueing assets.

@sarayourfriend

  • Old project with new focus. To asynchronously load TinyMCE for the freeform block in certain circumstances. Need help in figuring out the particularities of how TinyMCE is integrated into WordPress core. I think it could be a huge performance win if we could offload TinyMCE from the initial page load.

@hypest

  • Landed some fixes (adaptions to newer BlockEdit component is one), and an in-editor banner about deprecating the Classic editor in the apps.
  • In Progress: GSS support, Reusable blocks, removing ability to switch to the Classic editor, editor switch, dual-licensing Gutenberg, progress on Search block, progress adding search to the block inserter, progress on the embed block.
  • Blockers: We’re experiencing flakiness in the native mobile E2E tests, affecting many PRs and we’ll continue to work on fixing it.

@joen

@annezazu

  • Launched the next FSE call for testing and have been doing a fair bit of amplification.
  • Lots of feedback wrangling, issue testing, etc for the second call for testing with a draft in place for a summarized post.
  • Working on the next Core Editor Improvement post on the performance of the core editor itself.
  • Continued work on a “role of 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” post to clear up some confusion (TBD on when that’ll launch).

@ntsekouras

@aristath

@retrofox

@mamaduka

@mikeschroder

@poena

@nosolosw

  • I’ve been helping with reviews, bugfixing, and getting inner blocks working on the quote block. My focus for next week is going to be quote plus tackling some tasks for global styles.

Open Floor

Announcement

@mikeschroder
Gutenberg contributions are being prioritized by GoDaddy, so I’m spending time learning, and will be around the repo a bit more often. As part of that prioritization, I’m excited to welcome @mamaduka, who is joining the team full time for contribution to Gutenberg!

@annezazu
The third call for testing for the FSE Outreach Program that was launched yesterday! It’s centered around creating a custom (and fun) 404 page. Please help test or share the call for testing if you can’t — all of it helps. As always, join #fse-outreach-experiment if you want to stay tuned for more updates.

@priethor
I would like to raise awareness of the ongoing discussion on dropping support for IE11, and invite anybody that hasn’t already to give their feedback on the subject by March 18th.

An issue, PR and release.

@manooweb
Emmanuel wanted to bring attention to the PR: Add preload_paths filter for widgets screen and full site editing.
As well as this issue: Widget-id value used to build form field ids isn’t consistent with hidden widget-id field.

He was also wondering about releases and @annezazu shared https://make.wordpress.org/core/2021/02/11/making-wordpress-releases-easier/
Update: Let’s move forward with the March release, a July release (to give folks time to adjust their company plans), and a final release in December. I will create a plan to help us lessen the burden of releases, and in December I will see what we’ve accomplished and get some 2022/23 target release months published.

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