Dev Chat agenda, November 22, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 22, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

Dev Chat summary from November 15, 2023 – thanks @ironprogrammer and @webcommsat

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

What’s new in Gutenberg 17.1

Highlighted posts

Exploration to support Modules and Import Maps – this post shares the collaborative effort to explore native support for modern 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/. modules and import maps within the WordPress ecosystem to enhance the developer experience. Details of how you can get involved with this initiative are in the post.

Please add any additional highlighted posts in comments.

Introduction

Update from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor (New section in the agenda)

Initially items relating to this will be posted as comments on the agenda by @annezazu and others.

Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

WordPress release: 6.4 – any new issues?

Any new updates on 6.4.x release team or dates for 6.4.2?

Next major WordPress release: 6.5

Update opportunity.

Development cycle page.

Are you able to help with future bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs? Bug scrubs post.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

a) Josepha has asked in the Team Reps channel for highlights from the last year, if you have any item you feel should be included about core’s achievements or items in progress, please add them to the comments on this post for @webcommsat and @hellofromtonya who are preparing the bullet points to send for core.

b) Nominations for Core Team Reps: 2024 edition – reshare of the draft post to gather suggestions on timings related to the end date for nominations and the end of the voting period. The voting tool to use and whether an embedded voting 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. in discussion with other teams would be available for this edition to be finalized. Please do consider whether you could stand for the core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for next year.

#6-4, #6-5, #agenda, #dev-chat

Dev Chat Summary, November 15, 2023

The WordPress Developers Chat meeting took place on Wednesday, November 15, 2023 at 20:00 UTC in core on Make WordPress Slack (or #core in Matrix).

Key info

Announcements

🎉 WordPress 6.4.1 is out!: Thank you to every single person who has been involved and continues to contribute to 6.4! (Also see the original release post.)

Additional background information on the release:

Highlighted Posts

@webcommsat emphasized that developers with 6.4 knowledge can really help with reviews and contributions toward End User docs. The sooner the documentation is published, the sooner it can benefit the community.

And some items from last week’s cancelled chat to touch on:

@jeffpaul called on potential 6.5/6.6/6.7 leads to share their thoughts on this post.

  • Accessibility improvements in the 6.4 release: Check out this rundown of a11yAccessibility 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) items addressed in 6.4.
  • Proposal to discontinue the weekly #core-editor meetings: Add your thoughts about this change, and opportunities to incorporate editor discussions in Dev Chat.
  • Shareable performance testing utils: Join the discussion to explore ways that projects can incorporate performance testing as part of their development workflow.

And finally, some reminders ⏲️:

  • Call for 6.4.x Release Managers: Work on improving 6.4 continues after the main release, so please consider joining the 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. squad to help keep 6.4 healthy.
  • Call for volunteers to help with 6.4 end-user documentation: The Docs team is looking for volunteers to revise end-user docs (HelpHub) for 6.4. Check out the post and learn how to pitch in! Wait…did I mention this already? Yep — but it’s so important for our user community ❤️.

Release Updates

Next minor release: 6.4.2

@jeffpaul noted that if minor release squad volunteers can be found soon, that there’s a possibility of shipping a 6.4.2 minor release before year’s end. He requested feedback on whether there are any urgent/important items that need to be addressed soon.

@jorbin has been watching the (6.4) minor release issues report, and noted that #59847 seems the most urgent. He also pointed out nice-to-have editor package backports in #59828. If volunteers can be found to support the release, then he suggested a target of the week of November 27, 2023.

@joemcgill noted that #59847 is nearly ready, and requested feedback on the related PR.

👉🏻 Volunteers who can help with the 6.4.2 minor release (and determine timing) should drop a note in #6-4-release-leads.

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.: 6.5

  • The development cycle page has been created. It will be populated after discussing release timings and the finalization of the squad.
  • Are you able to help with future bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs? Check out the 6.5 scrub schedule.
  • And keep tabs on the #6-5-release-leads channel for additional updates.

@jorbin asked that 6.5 ticketticket Created for both bug reports and feature development on the bug tracker. scrub participants keep an eye out for regressions that should be moved to the 6.4.2 milestone, to get fixes delivered to users more quickly.

@webcommsat shared a link to the November 14 scrub for anyone looking at tickets async, and called on contributors to help with patches and writing of tests. 🙏🏻

Open Floor

Proposal to Cancel #core-editor Meetings

(This discussion started during highlights with regards to this proposal, and is shared here for readability.)

@jeffpaul expressed worry about losing touch with GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ development without regular meetings and sought alternative ways to stay updated. @jorbin suggested incorporating editor updates into existing meetings, particularly emphasizing involvement from major release editor leads.

@webcommsat highlighted the usefulness of core-editor summaries and proposed integrating regular updates into the dev chat agenda. @ironprogrammer raised the question of where the editor summary would originate if the meetings themselves were cancelled. @jeffpaul suggested obtaining editor updates during dev chat to ensure communication of updates and blockers across the project.

The idea of carving out an official “editor updates” section in dev chat was considered, and @jorbin suggested seeking volunteers from the #core-editor channel to participate in the chat. @annezazu volunteered to take on the responsibility and discussed potential ways to share editor updates, including during the meeting or through agenda posts. The need for asynchronous options, given different time zones, was acknowledged.

@webcommsat suggested having a dedicated section for editor updates on the dev chat agenda post, and plan for asynchronous sharing. @annezazu volunteered to make the meetings and incorporate asynchronous sharing, considering her near term availability across time zones. The importance of avoiding disruptions during meetings was discussed, as was the possibility of maintaining #core-editor office hours for specific questions related to the editor.

2024 Core Team Reps Nominations

@webcommsat gave a reminder for #core contributors to have a look at the draft post: Nominations for Core Team Reps: 2024 Edition. The dates/timing may need revising, and team reps are looking into the possibility of having the voting poll embedded into the post to make it easier to vote. Please share your feedback in #core and CC @webcommsat and @hellofromtonya.

WordPress 6.4 Retrospective

@cbringmann shared WordPress 6.4 Retrospective, and asked that anyone who has contributed to the release to reflect and share their thoughts on the release process (instructions in the post). A follow-up post will be published in December.

Next Meeting

The next meeting will be on 22 November 2023 at 20:00 UTC .

Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting!

Props @webcommsat for collaboration on this post and meeting preparation.

#6-4, #6-5, #dev-chat, #meeting, #summary

Dev Chat agenda, November 15, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 15, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

WordPress 6.4.1 became available on November 8, 2023.

For background information:

Highlighted posts

What’s new in Gutenberg 17.0

WordPress 6.4 performance improvements (this will be added to the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.). @swissspidy has also published his own post on how to get started with WordPress performance https://pascalbirchler.com/wordpress-performance-testing/

An update to the Field Guide with a new 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, and 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.: Main query loop handling for block themes in 6.4.

Post on an update to the core commit message format. It has been updated to take into account 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. and follow up commits. There is also a change on where ‘props’ is used in the commit message.

Call for what is currently needed with 6.4 End User documentation (HelpHub)
Documentation tracker on GitHub for 6.4 end users.

Reminder from last week’s schedule dev chat: (not all these may be featured in the dev chat on November 15 depending on time available).

Forthcoming release updates

WordPress release: 6.4 – any issues

Reference information:
Field Guide for 6.4
– All Developer Notes relating to 6.4 can be found using this tag.

Next major WordPress release: 6.5

The development cycle page has been created. It will be populated post the discussion on release timings and the finalization of the squad.

Are you able to help with future bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs? The next bug scrubs post.

Bug scrub on November 14, 2023. The list of tickets in milestone by the scrub. Start of the scrub for those looking at tickets async.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

This was due to be shared at last week’s dev chat. Bringing it again to November 15, 2023:
Nominations for Core Team Reps: 2024 edition – @webcommsat to reshare the draft post and timings. To continue exploring and with metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. to embed a voting 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. within the post to make it easier for voting. Thanks to @ironprogrammer on testing and helping move this option forward, which may also assist other teams in the future.

#6-4, #6-5, #agenda, #dev-chat

Dev Chat agenda, November 8, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 8, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

WordPress 6.4 is out!
Thank you to every single person who has been involved and continues to contribute to 6.4 related items. As the work continues on post release aspects, another update on props will happen later in the week. It can also capture anyone missed or WordPress IDs to be updated.

Highlighted posts

A proposal for 2024 major release timings has been shared by @chanthaboune. This includes proposed dates for 6.5 to 6.7. Thoughts on timing, focus, or anything else relates to these releases can be added to the comments.
In addition, depending on other items, the Dev Chat facilitator can give time during the meeting for a live discussion.

Accessibility improvements in the 6.4 release

Proposal to discontinue the weekly core-editor meetings. Discussion about incorporating some of this within Dev Chat.

Discussion on shareable performance utils to help incorporating performance testing as part of their development workflow. On a related note, a blogblog (versus network, site) is coming from @swissspidy to help people get started with performance testing.

Reminders:

Call for 6.4x release managers

Help write and review 6.4 End User documentation

Forthcoming release updates

WordPress release: 6.4 – any issues

Reference information:
Field Guide for 6.4
– All Developer Notes relating to 6.4 can be found using this tag.

Next major WordPress release: 6.5

The development cycle page has been created. It will be populated post the discussion on release timings and the finalization of the squad.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.4.x and 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps: 2024 edition – @webcommsat to reshare the draft post and timings.

#6-4, #agenda, #dev-chat

Dev Chat Summary, November 1, 2023

The notes from the weekly WordPress developers chat which took place on November 1, 2023 at 20:00 UTCin the core channel of Make WordPress Slack.

Key Links

Announcements

WordPress 6.4 Release Candidate 3 was released just before Dev Chat – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this.

Reminder: Dev Chat continues at 20:00 UTC throughout the year and does not change with daylight saving changes.

Highlighted Posts

A recording of the Hallway hangout on performance improvements in WordPress 6.4 is now available. The main points are also summarized on the post for anyone not able to access the recording.

Call for 6.4x release managers – this followed a discussion in Dev Chat last week. Please add a comment to the post if you are interested in supporting the maintenance and minor releases. Thanks to @jorbin for putting this together.

Reminder: Call for contributors to assist with 6.4 End User documentation. Extra assistance will be appreciated to help with this as we move towards the release day.

What’s new in Gutenberg 16.9.

Release Updates

Next major WordPress release: 6.4

Release candidates and rest of the cycle

RC3 was the last scheduled 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)..

@hellofromtonya explained that another RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). could possibly happen in the following circumstances. If 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.(s) gets reported and resolved, then yes, another might happen. But currently all regressions are resolved and shipped in RC3!

Next week’s schedule:

  • Dry Run – on Nov 6, 2023.
  • 24 hour code freeze starts after the Dry Run.
  • 6.4.0 release party starts on Nov 7, 2023 after the 24 hour code freeze expires.

Any issues relating to 6.4?

No other issues were raised during the meeting.

Relevant 6.4 links

No new links were published at the time of the meeting.

Field Guide for 6.4

@webcommsat: In addition to the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., you can also find all Developer Notes relating to 6.4 using this tag. If you think a change would benefit from an additional 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, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., please add it to the Documentation Tracker for 6.4. You can also 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.) one of the docs release co-leads in a message in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. if you want to discuss the possibility of an additional dev note and do not have access to the tracker.

Release parties schedule for 6.4

6.4 Release Candidates phase

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

6.4 Development Cycle

Future releases: 6.5

Timings and squad

  • @joemcgill followed up the question at last week’s dev chat on the formation of a release squad for 6.5.
  • @chanthaboune is thinking through the timing of releases across the year, and therefore there is no clear date for the first release of 2024 as yet. She hopes to bring a draft of suggested dates/ times by Monday November 6, 2023. This is the ‘only blockerblocker A bug which is so severe that it blocks a release.’ for a call for volunteers. One person has contacted Josepha so far to participate in 6.5.
  • General agreement in the meeting for early planning for the next release.
  • the discussion on Slack.

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets for 6.5

  • @oglekler requested triages to start as soon as possible, as trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is already open and 6.5 Alpha has begun. She raised a call for volunteers.
  • discussion followed on updating the core handbook to reflect that triages and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs can be held at any time, and to clarify that any contributors wanting to run a scrub did not need to wait for a completed release cycle or for a squad to be formed. The possibility of a post highlighting and calling for volunteers was suggested for the future.
  • a number of experienced core developers are able to buddy or give advice to help anyone less familiar with running scrubs.
  • if you can volunteer to run a scrub, you can share details in a future dev chat or comment on the summary post, and also post the information 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 ahead of time to best ensure that others are aware and can gather to help at the scrub. The core triage lead or the Core Team Reps can also update the bug scrub post in Make/Core.
  • if you are wanting to run a scrub related to particular component(s), please contact the component maintainers who can help and share information on priority tickets or planned scrubs.

The full discussion on triaging and bug scrubs.

Tickets or components help requests

No tickets were mentioned in the meeting.

Open floor

Reminders for the following were brought up right before the meeting ended:

Call for contributors to assist with 6.4 End User documentation. Volunteers can also post in this thread from the meeting.

Call for 6.4x release managers

Next meeting

The next meeting will be on Wednesday November 8, 2023, at 20:00 UTC.

After Dev Chat posts for attention:

Hallway Hangout: Issues Triage Extending Gutenberg – note this will take place on November 10, 2023 at 16:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel or contact one of the Core Team reps.

Props to @zunaid321 for contribution to the notes, and to @marybaum for review.

#6-4, #6-5, #dev-chat, #meeting, #summary

Dev Chat Summary, October 25, 2023

The notes from the weekly WordPress developers chat which took place on October 25, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

WordPress 6.4 Release Candidate 2 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this.

Summary and Insights of Phase 3 related conversations

WordPress 6.4 Release Candidate Phase

WordPress 6.4 Field Guide

Highlighted Posts

Summary and Insights of Phase 3 related conversations

WordPress 6.4 Release Candidate Phase

WordPress 6.4 Field Guide

Release Updates

Next major WordPress release: 6.4

New 6.4 related posts

6.4 Release Candidates phase

Update from contributors on docs for this release:

  • Field Guide for 6.4
  • You can also find all Developer Notes relating to 6.4 using this tag
  • If you think a ticketticket Created for both bug reports and feature development on the bug tracker. needs 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, and 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. and it has not been highlighted previously, send a message to Nalini 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/. for those working on the docs release or add it to the Documentation Tracker for 6.4
  • Call for contributors to assist with 6.4 End User documentation

Any issues relating to 6.4 tickets?

Existing 6.4 useful links

Release parties schedule for 6.4

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/

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/

What’s new in Gutenberg 16.9? (25 October) – Other than the new release update, nothing related to Gutenberg was brought up in the meeting.

Components & Tickets

The following tickets were raised in the meeting for feedback:

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #59718: Short-term (WP 6.4) hotfix to prevent fatal error in standalone Gutenberg (<16.5)

Trac ticket #59289: About Page for 6.4 Release

Trac ticket #59722: 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.: class-wp-rest-server.php

For the above tickets check out the Slack discussion for more information.

Trac ticket #59723: Pattern file containing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher constant from theme causes fatal error on update to WordPress 6.4 – was brought up by @hellofromtonya since this issue is in 6.3 and 6.4 and causes a fatal error during the upgrade process. Check out the Slack discussion for more info.

More tickets were brought up by @hellofromtonya as they need attention:

Trac ticket #59736: Regression: Singular 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. template – regression introduced in 6.4 by r56507. Has 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. on it and explanation.

Trac ticket #59723: Pattern file containing PHP constant from theme causes fatal error on update to WordPress 6.4 – fatal error during WP upgrade

Trac ticket #55493: [Block] File: Embedded PDF fails to render in Safari – regression in File block introduced in 6.4

Trac ticket #59732: Theme live preview is brokenCustomizerCustomizer 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. theme live previewers are broken, which 6.4 didn’t cause but help to emphasis it. There’s a patch that’s ready to test. Need to better understand its impact in 6.4.

Trac ticket #58281: Rollback Auto-Update (Rollback part 3) – check out the Slack discussion for more info as it was raised by @afragen

Open floor

@jeffpaul highlighted for post 6.4, the Community Summit Discussion Notes: Aligning processes and contributions between WordPress Core and Gutenberg. He especially drew attention to this topic to those who are active during the 6.4 release and particularly with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./Gutenberg interactions. He asked for them to share their insights and thoughts on the post to help improve planning, shared processes and to make things easier for the future.

@joemcgill raised a query on the planning and squads formation for the future 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., 6.5, and the 6.4.1, 6.4.2 etc minor releases. The Slack discussion.

Next Meeting

The next meeting will be on Wednesday November 1, 2023, at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props to @webcomms and @marybaum for input into the summary and for review.

#6-4, #6-5-2, #dev-chat, #meeting, #summary

Dev Chat agenda, November 1, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 1, 2023 at 20:00 UTC in the core channel of Make WordPress Slack. Note, the 6.4 RC3 is scheduled for November 1, so there may be a change in Dev Chat timings if needed. Please check the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel for updates.

Further items will continue to be added as they come up in core and release leads channels 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/..

Welcome and housekeeping

All are welcome to join Dev Chat.

If you can help with dev chat summaries, please raise your hand in the meeting. It is a busy time and additional people are appreciated.

Announcements

WordPress 6.4 Release Candidate 3 – was released today.

Highlighted posts

Due to time constraints during a release and to prioritize 6.4 items, some of the highlighted posts may not be raised during the live Dev Chat meeting.

Recording of the Hallway hangout on performance improvements in WordPress 6.4 is now available. The main points are also summarized on the post for anyone not able to access the recording.

Call for 6.4x release managers – this followed a discussion in Dev Chat last week. Please add a comment to the post if you are interested in supporting the maintenance and minor releases. Thanks @jorbin for putting this together.

Reminder: Call for contributors to assist with 6.4 End User documentation. Extra assistance will be appreciated to help with this as we move towards the release day.

What’s new in Gutenberg 16.9

Forthcoming release updates

Next major WordPress release: 6.4

Updates or important discussions relating to the final week of the release.

Any issues relating to 6.4?

Existing 6.4 useful links

Field Guide for 6.4

You can also find all Developer Notes relating to 6.4 using this tag. If you think another change would benefit from 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, and 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. and it has not been highlighted previously, add it to the Documentation Tracker for 6.4.

Release parties schedule for 6.4

6.4 Release Candidates phase

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/

Tickets or Components help requests

This section is subject to change depending on the needs of the release.

Please add any items for this part of the agenda to the comments – tickets for 6.4 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

#6-4, #agenda, #dev-chat

Dev Chat agenda, October 25, 2023

(Update – call for 6.4 end user documentation contributors)

The next weekly WordPress developers chat will take place on Wednesday, October 25, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Further items will continue to be added as they come up in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release leads channels 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/..

Welcome and housekeeping

All are welcome to join Dev Chat.

Summary of Dev Chat, October 18, 2023 – thanks to @ironprogrammer.

Announcements

WordPress 6.4 Release Candidate 2 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this..

Highlighted posts

Due to time constraints during a release and to prioritize 6.4 items, some of the highlighted posts may not be raised during the live Dev Chat meeting.

Summary and insights from discussions on Phase 3

Forthcoming release updates

Next major WordPress release: 6.4

Forthcoming milestone:

New 6.4 related posts

6.4 Release Candidates phase

Update from contributors on docs for this release:

  • Field Guide for 6.4
  • You can also find all Developer Notes relating to 6.4 using this tag
  • If you think a ticketticket Created for both bug reports and feature development on the bug tracker. needs 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, and 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. and it has not been highlighted previously, send a message to Nalini on Slack for those working on the docs release or add it to the Documentation Tracker for 6.4
  • Call for contributors to assist with 6.4 End User documentation

Any issues relating to 6.4 tickets?

Existing 6.4 useful links

Release parties schedule for 6.4

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/

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/

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.4 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticket if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

#6-4, #agenda, #dev-chat

Dev Chat Summary, October 18, 2023

The WordPress Developers Chat meeting took place on October 18, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

Highlighted Posts

  • WordPress 6.4 Release Candidate Phase: Learn or refresh your knowledge of what happens during RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).. Questions? Please post them in the comments.
  • 6.4 Dev Notes: It’s been a busy time in the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)! Stay updated on the latest technical updates by checking out posts conveniently tagged with #dev-notes-6-4. Major props to 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, and 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. authors and wranglers who have worked tirelessly to make this happen! 🎉
  • WordPress core is now using Playwright for all browser-based tests: e2e fans rejoice! This milestone promises improved test stability and better options for authoring tests. If you’ve been holding back while the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. from Puppeteer to Playwright has been underway, now is a great time to jump back in to improve Core e2e coverage.
  • What’s new in Gutenberg 16.8 (11 October): Check out updates to the Cover 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., Font Library, and more in this roundup of the latest release.

Release Updates

WordPress 6.4

RC 2 is scheduled for next Tuesday, October 24, 2023.

Stay in the 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. with 6.4 by following:

Additional release updates from the floor included:

  • A question was raised in #6-4-release-leads about removing some 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/-only packages from the next npm package update to Core.
  • Some 6.4 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, and 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. drafts are still needed for a couple of areas, so a gentle reminder was raised to keep the official 6.4 Documentation Tracker updated with latest progress. Reach out on the Tracker for help or to the Documentation release group in the #6-4-release-leads channel.

WordPress 6.3.2

  • WordPress 6.3.2 – Maintenance and Security release: This follow-up to 6.3.1 introduces several bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and security updates. Make sure to update!
  • Keep tabs on the #6-3-release-leads channel for future updates.

Open Floor

Automated Welcome/Signposting for #core

@webcommsat asked if Core would consider utilizing an automated messaging/workflow tool similar to that used by Training. When users joined the channel, they would receive a private message from Slackbot that includes channel-specific info and links, such as the Dev Chat schedule, or orientation for new contributors and contributor days. Abha agreed to draft a proposal to seek broader input from Core and new contributors.

Use of noopener noreferrer in New Window/Tab Links

@presskopp had a question regarding use of rel="noopener noreferrer" in links with target="_blank", which were supposed to have been removed. To help resolve instances where this unneeded behavior remains (in Core and Gutenberg), contribute to 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. #53843: Remove adding of rel=”noopener” to links with target=”_blank”.

Next Meeting

The next meeting will be on October 25, 2023 at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props @webcommsat for peer review of this post.

#6-3, #6-4, #dev-chat, #meeting, #summary

Dev Chat summary, October 11, 2023

Summary of the WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

Key links

Start of the Dev Chat meeting on the Core Slack

Dev Chat agenda followed – thanks to @webcommsat for preparing.

Announcements

  • WordPress 6.4 Beta 3 is available: Please help test and make the release the best it can be! Thanks to everyone who contributed toward 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. 3, as well as those who came and facilitated the release party on October 10. Note the Twenty Twenty Four images issue has been resolved, and the images are rendering correctly in Beta 3.
  • The WordPress 6.3.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. has moved to tomorrow, October 12, 2023 (more information under release updates to follow).

Highlighted Posts

  • Four Weeks in Core: Many thanks to @audrasjb for this update covering the amazing activity in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 4 and October 9, 2023:
    • 269 commits
    • 337 contributors
    • 295 tickets created
    • 43 tickets reopened
    • 277 tickets closed
  • Reminder: Hallway Hangout: Working session on consolidating various navigation modes: Taking place on November 15, 2023 at 16:00 UTC. This is part of efforts to improve 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) in the Site Editor.
  • The Dev Blog is looking for a writer for the following topic: How to add commands to the command palette. Please respond on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ ticketticket Created for both bug reports and feature development on the bug tracker. if you are interested.

Release Updates

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.: 6.4

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). 1 is scheduled for next Tuesday, October 17, 2023. 

This hallway hangout is happening tomorrow, October 12, 2023: What’s new for developers in WordPress 6.4

Stay in the 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. with 6.4 by following:

6.4 tickets that need attention

@rajinsharwar highlighted #52529 and requested testing of the 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. to see if they can replicate the errors mentioned.

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, and 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.

@webcommsat for the release documentation group: A reminder that the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is due to be published next week. This is so the link can be included in the release’s About Page. It would be great to have as many dev notes ready in draft as soon as possible, so they can have a final review and be published.

6.4 dev notes tracking project board for reviews and publishing is in progress.

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/ – Some Gutenberg tickets have already been labelled and clustered. There is a significant list that is being clustered and labelled, and these will then get added to the documentation tracker for 6.4. The tracker will show the edit, review and publish status of the dev notes – the view that will be most useful for this is ‘dev notes’. For Gutenberg, the wrangling and discussion on clustering and inclusions will happen in the Gutenberg tracker. Thanks to @bph who is going to be helping with this.

Core – If you are a component maintainer, and have not already shared that you are working on 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, and 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. relating to a Core Trac ticket or cluster of tickets, please add a comment on this issue and link any google docs, and we will populate the tracker with this.

For End user and Core tickets, the labelling is continuing. As we are being advised of dev notes needed or in progress by maintainers, they are being added to the documentation tracker.

For performance dev notes, issues are being added to the documentation tracker once confirmed for reviews and publishing purposes. Wrangling and discussion of inclusion of tickets is happening on the Performance GitHub ticket.

Reviews – If any devs are able to assist with technical reviews of dev notes if needed, let @webcommsat know to update the list.

Next minor release: 6.3.2

  • *A note on the 6.3.2 release schedule change:* In order to accommodate the need for hosts to deal with an important curl 8.4.0 security release on Wednesday, the 6.3.2 final release has been moved to Thursday, October 12, 2023.
  • Thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets in these releases! 

Gutenberg

Gutenberg 16.8.0 shipped during dev chat. An update on this release will be published soon and will be findable on the 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.) #gutenberg-new on the Make/ Core blogblog (versus network, site).

Component Maintainers requests

@rajinsharwar highlighted Trac ticket #55335. Requested confirmation if it should be considered 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..

Open floor

No additional items were raised. A reminder of the Field Guide and dev notes was shared.

Props to @webcommsat for the agenda and summary, and to @ironprogrammer for facilitating the meeting and reviewing the summary.

#6-3, #6-4, #dev-chat, #meeting, #summary