Tag Archives: dev chat

Sarah Norris 2:11 am on September 5, 2024
Tags: , , dev chat,   

Summary, Dev Chat, September 4, 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. The Road Map post was recently published.

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 WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.

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

The next Gutenberg release will be 19.2, scheduled for September 11.

Discussion

When discussing WordPress 6.7, we highlighted that @joen has listed some items that could use some help here, and @noisysocks reminded us that it’s always worth checking the Editor tasks board, especially items in the “Todo” and “Needs review” columns.

@peterwilsoncc asked for some additional eyes on this PR.

@noisysocks confirmed that the last Gutenberg 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). before the feature freeze is September 18, and these are the biggest items to keep an eye on:

Open Floor

@ironprogrammer asked: Has there ever been a pre-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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. online hangout where people could get this help beforehand? And maybe more importantly, would it do any good toward getting folks prepared before they arrive? – @joemcgill mentioned the documentation in the handbook and offered to reach out to the WCUS organizers to see if there is a need for more support with the onboarding process this year.

Props to @joemcgill for proofreading.

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

Joe McGill 1:26 am on August 29, 2024
Tags: , , dev chat,   

Summary, Dev Chat, August 28, 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.

The bug scrub schedule was published prior to the meeting.

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 WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.

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

The next Gutenberg release at the time of the meeting was 19.1, which was released on August 28.

Discussion

The first topic was, “which releases can be done during normal working hours for our CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech leads?”

@joemcgill referenced this comment on the agenda post and asked @peterwilsoncc to clarify the what was being considered.

I saw a comment in the 6.7 channel that release parties are also apparently going to happen in APAC times? I’d like to know if this was discussed in public somewhere. I know moving Dev Chat was discussed, but I (as 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). for 6.7) wasn’t included in the discussion about moving the release parties, neither before or after I accepted the role.

To summarize @peterwilsoncc response:

  • Beta release parties can happen during APAC sunlight
  • RCs will need to happen at around the usual time (~16:00 UTC) to allow for increased attendance
  • For the betas, @peterwilsoncc can drive MC and @kirasong and @noisysocks could do release commits
  • During RC, MC and commits will need to be people off the release squad

@joemcgill:

I’ll note that the time you’re suggesting for betas is well out of timezone for David who is the release coordinator. According to the handbook the first responsibility of the release coordinator is to “Run various release processes in Slack (beta, 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)., release)” but whatever you all work out seems fine.

@peterwilsoncc agreed to coordinate with the release squad about release timing will publish a post announcing the timing of release parties.

Next, @kirasong shared a list of issues that had been highlighted in #6-7-release-leads as things that folks can get involved with.

@noisysocks reminded that the Iteration/Tracking Issues column in the Editor tasks board is the best source of truth re. current initiatives.

Open Floor

We discussed the following issues:

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

Sarah Norris 5:13 pm on August 21, 2024
Tags: , , dev chat,   

Summary, Dev Chat, August 21, 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.

As the Dev Chat time has moved to 01:00 UTC, usual attendees may not be able to join as easily, so it would be great to see more folks taking advantage of the ability to suggest agenda items in the comments of the agenda posts each week. Posting things you plan to bring up during the open floor helps because we will prioritize time for those items and make sure they’re mentioned during the meeting—particularly if you’re not able to attend for any reason.

Announcements

Really excited to see the announcement about all of the new learning pathways that have been created recently. Read more 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 (6 weeks away)!

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 WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.

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

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

Discussion

On WordPress 6.7, @peterwilsoncc and @kirasong mentioned that a few tickets on the milestone have been tagged as needing early attention, so feedback on them would be appreciated.

@chaion07 and @stoyangeorgiev are drafting a Bug-Scrub schedule which will be published soon.

@annezazu mentioned that they are planning on assembling another release roadmap post for WP 6.7, which will also include many of the new features expected from the Gutenberg repo during the syncs in this release.

@peterwilsoncc highlighted the following that @noisysocks has mentioned:

  • 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.
  • 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
  • HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API

@dmsnell mentioned that the release planning for the HTML API is available in this issue. You can read more about the HTML API in the introductory post here and there are several related update posts.

In terms of other updates from the Gutenberg repo, there is already this project board that includes a lot of what is currently planned.

Open Floor

@mikachan raised #61708. @joemcgill asked: What happens to sites that are currently using that pattern in a template? Does the pattern stop being rendered, or is there a way to ensure that the change doesn’t adversely effect sites that are depending on it?

On #61708, @peterwilsoncc suggested: My suggestion would be soft deprecation and hide it from the inserter if it’s too poor quality for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@dmsnell raised #61833 and @peterwilsoncc offered to review this ticketticket Created for both bug reports and feature development on the bug tracker. soon.

On 61833, @elrae asked: I wonder if a similar fix needs to be thought of for the work being done on the GB dataviews stuff, I think they’re working on the quick edit stuff now. @dmsnell confirmed that they can look into it: I suspect that any fix for DataViews will be different as that will probably be sourcing its data from a different spot. this is a kind of jumble based on the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher templating.

@elrae also asked if more attention could be given to the following issue, Allow the sidebar to be a more flexible width: Particularly because there’s more and more push to get rid of old metaboxes. But developers don’t like sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. plugins because they’re too limiting and narrow.

@poena raised: One of the features that users asked for in Twenty Twenty-Five was support for post formats.
To be able to use post formats with the query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop., a new 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. needs to be added. I already mentioned this in core-editor but I need help from developers with 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/. experience to complete the changes.

Props to @joemcgill for proofreading.

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

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

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

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

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://2017.us.wordcamp.org/contributor-day/ 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

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

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://2017.us.wordcamp.org/contributor-day/ 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

Sarah Norris 12:44 am on July 31, 2024
Tags: , , dev chat,   

Summary, Dev Chat, July 24, 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 @hellofromtonya. 🔗 Agenda post.

Announcements

Congrats and thanks to everyone who contributed to these releases!

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.
  • Some fixes have already been backported to the 6.6 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
  • Currently reviewing fixes in the milestone.

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.

The 6.7 release squad is still TBD, and there will likely be an update posted soon.

@davidbaumwald asked some good questions about the combining of the MarComms role into the Release Coordinator role for 6.7. During the chat, we discussed that combining the roles could limit who might raise their hands in future releases. Please leave any further thoughts on the call for volunteers post.

Discussion

During discussion time, we talked about the proposal to move the dev chat’s time to an APAC friendly time during 6.7 cycle. There are 4 options presented and deadline for feedback is July 31. There doesn’t seem to be a clear solution, and we discussed a few questions, such as:

  • What if the 6.7 Release Coordinator is not in APAC? How does that affect the proposed times, if at all?
  • What if we share topics, concerns, questions, etc. in the Dev Chat agenda?

@clorith noted that anything that helps the 6.7 squad be efficient is ideal and that the goal behind the dev chat agendas being posted a minimum of 24 hours in advance gives folks who can’t attend a chance to raise topics.

Please share any further feedback on the proposal.

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

Sarah Norris 2:42 pm on July 18, 2024
Tags: , , , dev chat,   

Summary, Dev Chat, July 17, 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

Congrats to everyone for these releases! 🎉

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

WordPress 6.6.1 will be the first maintenance release following the 6.6 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.. Here are the tickets currently set for that milestone.

During the chat, @hellofromtonya, @ellatrix, @jorbin, @audrasjb, and @marybaum all offered to help with the 6.6.x releases. Thank you! ❤️

@hellofromtonya stated the current status of 6.6.1:

  • There are multiple reports of CSSCSS Cascading Style Sheets. specificity issues – causing all links to be underlined. A fix is ready. A test 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 is available. Have multiple test reports showing it fixes the issue with no side effects. But would be good to get more reports on affected sites.
  • 2 reports of fatal errors. One has a fix and the other is being investigated (I have a fix in mind).
  • Ella has been scrubbing in #core-editor.

@jorbin mentioned that there is also the $_old_files issue that is ready for a 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. in this release.

We discussed that a good time to release 6.6.1 would be sometime next week, as none of the issues mentioned are security-related, and this also gives us time to make sure there aren’t any further high-impact bugs.

Next major release: 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.

It looks as though there are still some members of the release squad that need to be confirmed from this post. @priethor mentioned that all the volunteers can be seen in the comments section of the call for volunteers post; nobody else volunteered via DM or similar.

@joemcgill followed up on a topic from last week, suggesting that for the 6.7 release, we move the time of these Dev Chats to a more APAC friendly-time since many of the release squad members in this release are located in that region and are unable to make these meetings.

I’ve followed up in #6-7-release-leads (reference) and there is interest in finding a more friendly time. Given the global nature of the project, there isn’t a perfect time that works for everyone to attend, so we’ll need to decide whether to move the time to later in the day (worse for folks in EMEA) or much earlier (worse for folks in the Americas). 

@joemcgill will follow up with a post to make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. about this.

Discussion

@afragen raised this ticketticket Created for both bug reports and feature development on the bug tracker. for 6.7: #53323. This places Hello Dolly in a containing folder to improve consistency with other plugins. Please leave any feedback directly on the ticket.

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-6, #6-7, #core, #dev-chat, #summary