Category Archives: General

Héctor Prieto 4:20 pm on August 16, 2024
Tags: , ,   

Hallway Hangout recording: Let’s chat about what’s next in Gutenberg (August 2024)

Covered topics

The following topics were demoed:

Recordings

Below, you can find the recording of the first half of the session:

Due to technical reasons, the second half of the session couldn’t be recorded. Fortunately, the latter demos were prerecorded and can be found below:

Zoomed-out mode

Author: @scruffian

Grid Layout

Author: @andrewserong

Background Image blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. supports

Author: @andrewserong

Thanks to everyone for joining and participating! Special props to @mikachan, @grantmkin, @jffng, @madhudollu, @santosguillamot, @ajlende, @ntsekouras, @scruffian, and @andrewserong for presenting, and to @richtabor for jumping in to facilitate while I was going through technical issues.

#gutenberg, #hallway-hangout #outreach

Beatriz Fialho 3:42 pm on August 15, 2024
Tags: , , ,   

Introducing Twenty Twenty-Five

The WordPress 6.7 release will feature a new default theme: Twenty Twenty-Five.

Four public domain film photographs: one showing a historical building, the other a close up of flowers, the other shows birds and the other an African woman. Below it is written Twenty Twenty-Five.

Concept

While ideating Twenty Twenty-Five, one recurring idea was that simple things should be intuitive while complex things should be possible. This concept of simplicity and complexity leads to a reliable foundation for extending a default WordPress experience to make it yours.

Twenty Twenty-Five embodies ultimate flexibility and adaptability, showcasing the many ways WordPress enables people to tell their stories with many patterns and styles to choose from. The glimpses of natural beauty and ancestry woven into the theme evoke ideas of impermanence, the passage of time, and continuous evolution.

The demo content imagery, all from the Public Domain, carries a poetic, universal, and ubiquitous tone that complements the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. concept. There was an opportunity to visually lean into a positive tone to bring softness, lightness, and inspiration through its aesthetic.

A collage kind of composition showing many of the photographs used in the 2025 default theme.

Patterns

Structurally, Twenty Twenty-Five offers a robust set of patterns, promoting interoperability and enabling users to compose intentional pages quickly. A broad range of patterns was designed for categories such as services, about, landing pages, products, calls to actions, events, and others.

A broad range of patterns designed for the 2025 theme in categories like services, about, landing pages, products, calls to actions, events, etc.

Styles

Given the theme’s global use, high-quality and comprehensive fonts that support multiple languages have been considered from the first conceptual steps of the design. Furthermore, we’re refining a set of diverse color palettes to be bundled within the theme as style variations.

Eight different color palettes that were designed for the 2025 default theme.
Eight different typography pairings that were designed for the 2025 default theme.
Showing nine examples applied to different templates of style variations designed for the 2025 theme.

Templates

Twenty Twenty-Five also features a versatile set of blogblog (versus network, site) templates: text-centric blogs with sidebars, photo blogs that highlight featured images, and more complex blogs with diverse content. Twenty Twenty-Five will be fully compatible with the Site Editor and will use many of the new design tools like the Grid 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 Pattern/Section Styles.

Personal Blog (Default)

In keeping with the idea of simplicity, the personal blog tendency is to lean on a default template that just works, whether you want to write a post with a title and featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. or not, and showing all the post’s content out-of-the-box, instead of just excerpts.

Two mockups: the one on the left shows blog posts with an image, a post title and the full content of the post and the one on the right shows a single post.

Photo Blog (Alternative)

The alternative “photo blog” templates tailored primarily for photography or portfolios lean on an image-heavy approach, with interesting layouts that can be used for a variety of purposes.

Two mockups: the one on the left shows just the featured image of blog posts and the one on the right shows a single post with a full width image.

Complex Blog (Alternative)

Lastly, the set of complex blog alternative templates would be more suitable for websites with greater complexity in content. Some of these templates, with more variety in type scales and more opinionated designs can also appeal to different audiences.

Two mockups: the one on the left shows a 3 column grid with blog posts containing featured images and post titles followed by a 2 column grid, and the one on the right shows a single post with a big left-aligned title, post meta and a wide image, followed by post content with a sidebar on the right.

Development

As part of the 6.7 release, Carolina Nymark (@poena) and Juanfra Aldasoro (@juanfra) are leading development while Beatriz Fialho (@beafialho) is leading design. If you’re interested in contributing, make sure you’re following this blog; we look forward to your involvement and support throughout the process. 

The Figma file is the design source of truth. Comments in the main file are open, and anyone should feel free to duplicate the Figma to their drafts and remix. Both of these actions are free, whereas every edit access is paid and therefore reserved.

Theme development will happen on the Twenty Twenty-Five GitHub repository. You can contribute by submitting and reviewing pull requests or opening new issues and, as usual, once the theme is stable, it will be merged into Core and 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 by the repository owner. https://github.com/ repository will be archived.

Starting on Wednesday August 21st at 3:00 PM UTC , there will be weekly Slack meetings in #core-themes to coordinate development of the theme. Agenda notes will be posted before meetings and summaries posted after the meeting.

Learn more

For information about previous default themes, read the following posts:

Here are a few resources if you’re interested in learning more about Block Themes and the Site Editor:

+make.wordpress.org/themes/

Props @richtabor, @karmatosed, @priethor, @poena, @cbringmann and @joen for helping co-create this post and to @luminuu for proofreading it.

#6-7, #bundled-theme, #twenty-twenty-five

Joe McGill 9:10 am on August 15, 2024
Tags: , , ,   

Summary, Dev Chat, August 14, 2024

Start of the meeting in 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/, facilitated by @mikachan. 🔗 Agenda post.

Announcements

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/ 19.0 was released earlier today 🎉 You can read the release post here.

The WordPress 6.7 release squad was announced just before this meeting! You can find the list of squad members here.

Forthcoming Releases

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

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1.

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

The next maintenance release will be 6.6.2. @hellofromtonya shared in the meeting that the release date may be delayed by a few weeks to early September to address all of the CSSCSS Cascading Style Sheets. specificity issues being tracked in this Gutenberg issue. Once a date is confirmed, Tonya will post an update on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. site.

Next Gutenberg release: 19.1

The next Gutenberg release will be 19.1, scheduled for August 28.

Discussion

Update on changing the Dev Chat time for 6.7 – Now that the release squad for 6.7 has been announced, @joemcgill is going to give them an opportunity for feedback on the original post, and then confirm an updated Dev Chat time starting next week. Currently, Wednesday, Aug. 21 at 1:00 UTC is looking likely.

@karmatosed reminded that we should make sure to post agendas maybe day before and ask those not attending due to time zone to get their updates added. It will need to be a habit for some.

@clorith suggested some ideas for automating the agendas to make it easier to publish at a consistent time each week.

Open Floor

@dmsnell is asking for additional feedback on #61864. To summarize:

[this] fixes old commits and errors caused by our subversion-to-git process, as noted in the 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.. For example, a number of contributors are stuck with corrupted names because the conversion script double-UTF-8 encodes text from the WordPress.org profiles.

it’s a one-off thing I proposed, but in the future allows each contributor to have control over their own representation. we don’t have to maintain it because we simply haven’t been maintaining this stuff at all. it doesn’t particularly go out of date, but a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. may change their name and not update the file. it’s their option to do so or not

if there’s no problem there’s no need to be added to the list. for example, I have no commits from the time a GUID was added as the email domain, and I haven’t changed my name. so I’m not in the list. only people who have commits from multiple identities and people whose names have been corrupted by the conversion are in the list right now.

Props to @mikachan for proofreading.

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

Robert Anderson 1:31 am on August 15, 2024
Tags: , , ,   

Automatic conversion of HEIC images to JPEG in WordPress 6.7

In WordPress 6.7, HEIC image uploads will be automatically converted to JPEG on the server when possible.

This allows you to view HEIC images in WP Adminadmin (and super admin) and use them in posts
and pages regardless of whether a visitor’s browser supports HEIC. Browser support for HEIC is low while the occurrence of HEIC images is common as they are the default storage format used by Apple devices.

 
The original HEIC image can be downloaded via a link on the attachment page.

Screenshot of an attachment in WordPress with 'Original image' field circled

Conversion is only done if the server has a version of Imagick that supports HEIC. You can see whether a server supports HEIC in Tools → Site Health → Info → Media Handling → ImageMagick supported file formats.

Screenshot of the 'ImageMagick supported file formats' field in WordPress

If conversion is not possible, a warning is displayed to the user encouraging them to manually convert the image to JPEG. This was the default behaviour prior to WordPress 6.7.

Screenshot of an error message in WordPress informing the user that the image cannot be displayed in a browser

Automatic conversion of HEIC images to JPEG can be disabled using the image_editor_output_format 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..

add_filter( 'image_editor_output_format', function( $output_format ) {
    unset( $output_format['image/heic'] );
    return $output_format;
} );

#6-7 #core-media #dev-note #dev-notes #dev-notes-6-7

Dennis Snell 10:58 pm on August 14, 2024
Tags:   

Control your contributions with mailmap

In [58899] a .mailmap file was added to WordPress which instruct git and git-aware tooling to alias specific emails and names to a new identity. With this change it’s possible to combine multiple git identities into a single one as well as fix any identities which may be broken in history.

For example, there was a time commits were brought over from Subversion and the emails associated in the git commit followed the form <username@602fd350-edb4-49c9-b593-d223f7449a82>. For each of these users, there might be other commits referencing <username@git.wordpress.org>. Tools counting commits, history logs, annotations (blames), and others will make it seem as though the commits came from different people.

Further, committers change their names from time to time. Since git history is immutable there’s no easy way to update old names without rewriting the entire project. The .mailmap file provides the necessary mechanism to do this without interrupting that history.

Finally, committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. names may be corrupted if they contain non-US-ASCII characters. This corruption can be resolved by adding an entry in the .mailmap file correcting the name. This was the motivating case for introducing this file.

Most git tools provide a way to see the underlying raw data, so to see the actual recorded names it’s usually possible to pass --no-use-mailmap.

Would you like to review your own contributions?

If you run git shortlog -ens from the wordpress-develop repo then it will show a listing of commits per committer. If you see any problem with your name, duplicate name/email pairs, or would prefer to update your name, you can add new entries in the .mailmap to make the appropriate adjustments.

# Review variations of my name before adding the .mailmap entry
git shortlog -ens | grep -iE 'dmsnell|dennis'
    98	Dennis Snell <dmsnell@git.wordpress.org>
     1	dmsnell <dmsnell@602fd350-edb4-49c9-b593-d223f7449a82>

echo "Dennis Snell <dmsnell@git.wordpres.org> dmsnell <dmsnell@602fd350-edb4-49c9-b593-d223f7449a82>" >> .mailmap

git shortlog -ens | grep -iE 'dmsnell|dennis'
    99	Dennis Snell <dmsnell@git.wordpress.org>

#meta

Héctor Prieto 7:49 pm on August 14, 2024
Tags: ,   

WordPress 6.7 release squad ready

This post is a follow-up to the WordPress 6.7 call for volunteers.

Exciting News: The WordPress 6.7 Release Squad is assembled!

Notes and feedback

  • This squad experiments with merging the Marcomms lead with the release coordinator, as suggested in the previous proposal and agreed upon with this release’s coordinator, David. We’re open to feedback and can revert this change during the process if needed.
  • While announcing the whole release squad is ideal, at the end of the day, it involves a lot of async coordination that delays the announcement. Feedback received indicates this is particularly constraining for the Default Theme Role, for which the leads had to start the work before this announcement to avoid getting caught by the release deadlines. For future releases, I suggest:
    • Providing release squad updates every week.
    • Making a call for volunteers for the default theme earlier, independent of the squad of the release that will contain it.

Big thanks to everybody who volunteered for the release squad!

Thanks to @chanthaboune and @cbringmann for reviewing this post.

#6-7 #planning

Jorge Costa 1:19 pm on August 14, 2024
Tags: , , ,   

What’s new in Gutenberg 19.0? (14 August)

“What’s new in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.

In the Gutenberg 19.0 release, two important features have been added under experimental flags to allow folks to opt in to test and give feedback as they want. These features can be enabled by going to Gutenberg > Experiments. The first feature lets you connect blocks to custom fields, which many have been eager to see. The second feature lets you quick edit within the new Site Editor > Page’s interface, built using Data Views. Feedback is welcome and needed for both.

Outside of these experimental features, this release also includes severable notable enhancements, including a more intuitive user interface to configure views (pages, templates, patterns, etc) and the option to choose whether filters are shown or hidden within them. Finally, the option to manually enter a zoomed out view was added alongside the device preview options and multiple writing flow enhancements were completed.

  1. UI to connect blocks and custom fields
  2. Quick edit is now available on the new Pages list
  3. Show or hide filters in Data Views
  4. Changelog
    1. First-time contributors
    2. Contributors

    UIUI User interface to connect blocks and custom fields

    Gutenberg 19.0 comes with the first UI prototype to connect blocks and custom fields. It has been merged under an experimental flag in 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..

    To check it out enable the “UI to create 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. bindings” experiment under “Gutenberg -> Experiments”.

    Quick edit is now available on the new Pages list

    The first version of Quick Edit for Data Views has landed in Gutenberg 19.0 as an experiment. It allows users to edit some fields without leaving the overall Pages interface — it supports bulk editing as well.

    Show or hide filters in Data Views

    Gutenberg 19.0 includes functionality to hide/show the filters in the user interface. This simplifies the Data Views UI, as complex filters (including default ones for some views) will no longer occupy UI space. At the same time, feature parity and ease of use are maintained, as filters can still be added by clicking the filtering button when needed.

    Changelog

    Continue reading →

    #block-editor, #core-editor, #gutenberg, #gutenberg-new

    Sarah Norris 2:49 pm on August 8, 2024
    Tags: , , ,   

    Summary, Dev Chat, August 7, 2024

    Start of the meeting in 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/, facilitated by @joemcgill. 🔗 Agenda post.

    Announcements

    There were no announcements this week.

    Forthcoming Releases

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

    We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1.

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

    The next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.

    Next GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release: 19.0

    Gutenberg 19.0 is scheduled for August 14. RC1 was released on August 7.

    Discussion

    @joemcgill led with this reminder:

    WordCamp US is coming up on September 17–20, and @courane01 has begun requesting table leads from all the Make teams for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. We can use some time to discuss this and answer any questions folks might have.

    Open Floor

    #53817 was raised in the agenda comments. We discussed that this issue should be opened in the Gutenberg repo instead of TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., which @hellofromtonya offered to handle.

    Next, we discussed #51525. @mathieulamiotwpmedia described where the ticketticket Created for both bug reports and feature development on the bug tracker. was up to:

    We are interested in this possible enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. for a while and we built a library that we currently use based on the ticket’s discussions. Having this directly in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. would open up a few possibilities to make apply_filters typing more resilient, but it was never really clear in the ticket discussion if such approach could make it to the Core at some point.

    So, we suggest 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. based on the library we built, and it would be great to get feedbacks from Core maintainers. First, to know whether or not it’s worth pursuing the effort on this, from a WP Core perspective. And if yes, what could be next steps

    The ticket itself is loaded with information and context, and the patch itself might not be easy to assess right here right now ; but I thought we could bring this up here to maybe follow-up on it asynchronously. That’s it, I guess!

    We discussed whether this should be included in Core, how it could be used, or if it is intended as a shared 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. that plugins and themes would use.

    Finally, @swissspidy mentioned this merge proposal for Preferred Languages that resulted in some good feedback, including:

    • Concerns that core starts consuming GB packages outside of the editor
    • Tooling limitations in core (no TypeScript, no ESLint, no Jest tests)
    • Concerns about adding TypeScript to core (implications for build server etc.)
    • Need to have performance tests with fallback chain as well

    @swissspidy will publish a new make/core post following this feedback.

    Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

    Props to @joemcgill for proofreading.

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

    Birgit Pauli-Haack 8:08 am on August 5, 2024
    Tags: , , ,   

    Developer Blog editorial meeting summary 1 August 2024

    Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make 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/. Start of the meeting in Slack.

    Attendees: @milana_cap, @oglekler, @ironnysh (async), @bcworkz (async) and @bph (facilitator).

    Last meeting notes: Developer Blog editorial meeting summary 4 July 2024

    Newly published post since the last meeting: 

    Since the last meeting, we published the following articles

    Huge Thank You to the writer and reviewers! 

    Project Status

    The project board for Developer Blog content is 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 by the repository owner. https://github.com/.

    In review

    In Progress:

    Post on the To-do-list, assigned to writers.

    Topics, approved, in need of a writer

    If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph in Slack either in the #core-dev-blog channel or in a DM.

    New Topics approved

    The latter is part of the roll-out of video content type for the Developer Blog, proposed and approved during a meeting on July 4th, 2024: “The next step is that Ryan will submit an overview of all directives of the Interactivity 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. and provide an example of the first video. It will also be the test drive of the suggested process from which we can iterate afterward.“

    Next meeting: September 5, 2024, at 13:00 UTC in the #core-dev-blog channel

    Props to @oglekler for the review of the post.

    #meeting, #meta, #summary

    Joe McGill 8:50 am on August 1, 2024
    Tags: , , ,   

    Summary, Dev Chat, July 31, 2024

    Start of the meeting in 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/, facilitated by @mikachan. 🔗 Agenda post.

    Announcements

    There were no announcements this week.

    Forthcoming Releases

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

    @hellofromtonya confirmed the status of 6.6.2:

    • No schedule yet for it.
    • @hellofromtonya and @jorbin suggested tentatively scheduling a regular maintenance release for late August unless something critical requires that schedule to change.

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

    We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1.

    @jorbin asked what timeframe we want to consider early for the purposes of the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. keyword. There was no consensus in the meeting, but this provides an opportunity to improve our documentation to avoid confusion about what this keyword means. @joemcgill offered to review if someone wants to attempt to improve the docs about the early keyword in our handbook.

    @mikachan reported that she checked in with @priethor about an update on the release squad for 6.7 and expects to have an update sometime next week.

    Discussion

    @mikachan led with this update:

    I’d like to note that WordCamp US is coming up on September 17–20, and @Courtney has begun requesting table leads from all the Make teams for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Please let her know if you’re interested in leading a table for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, and feel free to ask questions in #core.

    Open Floor

    @nikunj8866 raised two issues for discussion:

    • #40477
      • @joemcgill suggested that this could use a review from a 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/ maintainer
      • @hellofromtonya identified the need for an owner and automated tests
      • @spacedmonkey offered to take a look
    • #13459
      • @jorbin suggests that it needs automated tests

    @spacedmonkey raised a question about #60414:

    What defines “ready to commit” for this ticketticket Created for both bug reports and feature development on the bug tracker. and tickets of this size? What are the next steps to get a ticket like this merged into core? How many core committers need to sign off on it? Can it be committed in WP 6.7?

    This question was previously raised and discussed in this #core-committers conversation in Slack and summarized by @hellofromtonya in this Trac comment.

    @jorbin identified the biggest thing needed to move this forward is having multiple committers who are willing to drive consensus and finalize the implementation before it is committed. @hellofromtonya shared these three proposed steps that @jorbin had previously shared in the Slack conversation:

    1. Getting 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. on a dotorg sandbox and making sure it doesn’t blow up .org.
    2. Getting this on a large host so we can see how it performs in the myriad conditions core runs
    3. Making sure that wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ doesn’t break

    Additional conversation about the proposal ended with @mikachan suggesting that a good next step might be an updated post for make/core, since there are still many questions to resolve.

    Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

    Props to @mikachan for proofreading.

    #6-7, #dev-chat, #summary