Tag Archives: 6-7

Sarah Norris 7:14 pm on November 14, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, November 13, 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

WordPress 6.7 “Rollins” was released on November 12, 2024. A big thank you to everyone who contributed to this release!

To quote the release post:

WordPress 6.7 reflects the tireless efforts and passion of more than 780 contributors in countries all over the world. This release also welcomed over 230 first-time contributors!

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

We are currently in the WordPress 6.8 release cycle.

Next maintenance release

There are no maintenance releases planned at this time.

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

The next Gutenberg release will be 19.7, scheduled for November 20.

Discussion

There were two main topics today:

  1. Immediate issues that need to be addressed following the release
  2. Confirming volunteers to coordinate upcoming maintenance releases following 6.7

There are currently no immediate issues requiring a quick 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., so the first minor will likely be released in around 30 days.

@azaozz mentioned #62401 as something that may need addressing soon, but it is from 6.6 rather than 6.7.

@oglekler also raised #62413 for potential inclusion in the next minor release.

We also discussed the need to start to identify volunteers who are willing to help with minor releases as they are ready. We already have a list of 21 issues (1 fixed) set to the 6.7.1 release milestone. @joemcgill suggested we do a call for volunteers if needed next week.

Props to @joemcgill for proofreading.

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

Sarah Norris 1:06 pm on November 6, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, November 6, 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

WordPress 6.7 RC 3 has been released. Thanks to everyone who participated in the release party.

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 dry run is scheduled for Monday, November 11, with the full release scheduled for Tuesday, November 12. For specific release times, review the release party schedule post.

There are a couple more items that need to be backported since 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). 3, such as 62305. 62061 also 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. which includes a list of changes that were made during this release related to improving PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.4 support, which @desrosj and @marybaum offered to help with.

Next maintenance release

There are no maintenance releases planned at this time.

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

The next Gutenberg release will be 19.6, scheduled for November 6.

Discussion

@peterwilsoncc has requested that we follow up the the following list of items during Dev Chat, if they have not already been resolved by then:

  • Status of TT5 (cc @poena @juanfra), will need to be async due to timezones
  • Status of GB packages (cc @get_dave @kevin940726)
  • Following tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets need 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. sign-off for 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.

@peterwilsoncc confirmed that most of the backports in that list are complete: #62305 is the only one remaining. @get_dave reported packages were done. @joemcgill noted there are some remaining commits for Twenty Twenty-Five to come in. As there are several commits landing after RC 3, there is a plan to do a silent RC 4 ahead of the dry run next week, likely on November 7.

Open Floor

@justlevine requested some feedback on the following:

Id love to get some eyes/feedback on the PHPStan config over on https://core.trac.wordpress.org/ticket/61175 .

The errors detected there have already resulted in a handful of merged PRs (via https://core.trac.wordpress.org/ticket/52217 ) including a bugfix in 6.7, so already showing its worth.

@desrosj offered to help progress these.

Props to @joemcgill for proofreading.

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

Sarah Norris 10:10 pm on October 30, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, October 30, 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

WordPress 6.7 RC 2 was released on October 29. Thank you to everyone who contributed to this release and attended the release party!

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 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). 3 is scheduled for Tuesday, November 5. For specific release times, review the release party schedule post.

There are a few open issues on the next major report. @peterwilsoncc mentioned that @adamsilverstein and @azaozz have been working on some fixes for HEIC images that have been committed to 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. (#62272 and #62305). Most other items are tasks to make sure the old files list is updated, editor commits, etc.

#61094 was also recently reopened, which should hopefully be quick to review.

Next maintenance release

There are no maintenance releases planned at this time.

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

The next Gutenberg release will be 19.6, scheduled for November 6.

Discussion

@poena gave an update on TT5:

There are still text string changes that needs approval from the Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. since we are past the string freeze in 6.7. Because of that, the string changes did not make it into RC2. It seems unclear how to get the approval or who can give it.

There are still changes being made to how some colors are applied, both to improve the user experience and the color contrast ratios.

After Dev Chat, @audrasjb helped to approve and commit the string changesets for TT5.

@joemcgill raised: Seems like last release, there was a lot of last minute coordination around marketing efforts to unify content between the about page and a standalone site for the release. Any idea how those efforts are coming along this release?

@ryelle confirmed that this should be all good; the content for the About page is the same as the release page, and was finalized with RC1. Tracking the wp.org release page is here: https://github.com/WordPress/wporg-main-2022/issues/506.

Open Floor

@joemcgill asked: I’d like to get some input about when we should consider moving these Dev Chat times back to the original time, before we changed it for this release cycle. I still think that this time shift was a good idea to enable more of the release squad to attend. However, the impact has definitely been lower engagement.

It was discussed that the earliest date to move back to the original time of 20:00 UTC would be November 20, after the 6.7 release, just in case there is some early follow-up that needs input from release squad Tech Leads that would otherwise not be able to attend.

Props to @joemcgill for proofreading.

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

Sarah Norris 2:41 pm on October 17, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, October 16, 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

WordPress 6.7 Beta 3 was released on October 15. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.

Props to everyone who helped get this release out!

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 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). 1 is scheduled for Tuesday, October 22. For specific release times, review the release party schedule post.

@peterwilsoncc confirmed that the release party times are set to change for the rest of the release cycle to the usual 4pm UTC or thereabouts.

Next maintenance release

There are no maintenance releases planned at this time. However, @ironprogrammer has added #62173 to the next minor milestone for consideration.

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

The next Gutenberg release will be 19.5, scheduled for October 23, and will include the following issues.

Discussion

@marybaum raised this question earlier…

Do we want to discuss string freezes and commit processes?

@peterwilsoncc confirmed that after the release of RC1 there is a soft string freeze:

That basically means a string freeze for everything except for the about page, so translators can begin the hard work of making WP available in many many languages on the day of release.

The exception to the rule is that buggy strings can be fixed. A buggy string is one that can’t be translated properly. 

There was a discussion about when the soft and hard string freezes could happen, with @joemcgill suggesting: I think giving as much affordance to the #polyglots team as possible during this cycle would be advisable.

On the commit process, @joemcgill mentioned that after the 6.7 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". is cut, all new commits to that branch should first be made in trunk and then backported using the backport process outlined in the handbook.

Open Floor

During the open floor, Earle Davies highlighted that ACF had a security update today that presumably needs to get its way back into secure custom fields. @jorbin suggested #secure-custom-fields as the best channel for these discussions. @joemcgill also mentioned that if you want to report a security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. with a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, you can follow these instructions.

Props to @joemcgill for proofreading.

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

Joe McGill 10:38 am on October 9, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, October 9, 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

WordPress 6.7 Beta 2 was released on October 8. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.

During the meeting, @peterwilsoncc and @marybaum updated the Playground link in the news post to correctly load WP 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. 2.

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 Beta 2 is scheduled for Tuesday, October 8. For specific release times, review the release party schedule post.

@peterwilsoncc shared that there’s been a change in the release squad. @get_dave will be replacing @noisysocks in the co-editor tech lead role. Kai will remain as the other editor tech lead. The WP 6.7. release page will be updated to reflect the addition of @get_dave while keeping @noisysocks as a listed co-lead to acknowledge his contributions to this release.

Next maintenance release

There are no maintenance releases planned at this time.

However, earlier in the #6-6-release-leads channel, @hellofromtonya mentioned…

This week, continuing to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets reported against 6.6.x (ie Version).
Then can do a 6.6.3 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub in #core to help with assessment and resolutions.

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

The next Gutenberg release will be 19.4, scheduled for October 9, and will include the following issues.

Discussion

There were no discussion topics raised this week, so @joemcgill shared the following issues that were raised in the #6-7-release-leads channel:

From @ndiego (link):

A reminder that there are a number of bugs on the 6.7 Editor project board that need addressing. Specifically, the new Zoom Out Mode has many issues. Most are minor, but additional help on these would be great.

From @joen (link):

One issue that could use your eyes is 65644. It’s a pretty unfortunate bug, given TT5 will heavily rely on section styles. If you can help fix this issue, or know someone who might be able to, please reach out!

@peterwilsoncc asked for feedback on #59684. Specifically, wondering where where wp_save_image is tested so he can ensure he doesn’t break 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. data in an attempt to fix it. @joemcgill agreed to follow up after the meeting.

Open Floor

Brad V asked for clarity about whether PRs for default themes should be made against wordpress-develop.

@peterwilsoncc confirmed:

For the bundled themes, yes, they are maintained in WordPress-Develop.

You can open a ticketticket Created for both bug reports and feature development on the bug tracker. on https://core.trac.wordpress.org/newticket?component=Bundled+Theme if it doesn’t already exist.

And create a PR against https://github.com/WordPress/wordpress-develop/ with a link to the ticket in the description.

Props to @mikachan for proofreading.

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

Sarah Norris 1:51 am on October 3, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, October 2, 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

WordPress 6.7 Beta 1 was released on October 1. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.

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. 2 is scheduled for Tuesday, October 8. For specific release times, review the release party schedule post.

@peterwilsoncc noted that the release is now in the phase of 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 only. No further enhancements or features can be committed to WordPress-Develop until the 6.7 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". is forked in a few weeks time after 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). 1. Tasks can also be completed at this stage, such as the about page, etc.

@peterwilsoncc also mentioned that the Twenty Twenty-Five theme is still being worked on in 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/ repository and he’s sure the theme team would love assistance there https://github.com/WordPress/twentytwentyfive/issues.

https://core.trac.wordpress.org/ticket/49985 could do with some eyes on it and is currently in the 6.7 milestone. Also, getting eyes and follow-ups on the items marked as needing changes in the milestone report by workflow would be helpful.

On the Editor side, @noisysocks suggested diving into fixing bugs that are in the 6.7 board if you’re interested in helping out.

Next maintenance release

There are no maintenance releases planned at this time. Currently, the next minor report is clear.

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

The next Gutenberg release will be 19.4, scheduled for October 9, and will include the following issues.

Discussion

There were no discussion topics raised this week.

Open Floor

@akirk left a comment on the agenda asking whether the WordPress project wanted to be represented at FOSDEM 2025, happening in Brussels this coming Feb. To quote his comment on the agenda:

I believe bringing a dedicated WordPress room to this open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. conference could be beneficial for WordPress to connect more with other open source projects. We could select talks for the devroom (given that they’d be proposed) that can inspire and take inspiration from other open source projects, for example about WordPress Playground, or how the WordPress project does translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..

Proposals need to be submitted by Oct 10. Alex is looking for feedback about whether it makes sense to engage in the FOSDEM environment and to gather interest in submitting talks if the room is accepted. Please reach out to @akirk directly if you’d like more information about this.

Props to @joemcgill for proofreading.

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

Joe McGill 10:04 am on September 25, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, September 25, 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 are no announcements this week. However, last week many from the community attended WordCamp US 2024 in Portland, OR. If you missed it, or just want to reminisce, several folks contributed to this PDX + WCUS 2024: A Recap post from the 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 one week away. The Road Map post can be found here.

In case you missed it, @davidbaumwald just published the WordPress 6.7 Release Party Schedule.

@peterwilsoncc reminded that all enhancements need to be committed prior to the beta so folks wishing to get something in should do so sooner rather than later.

The final release of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for WP 6.7 has been released and the 6.7 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". for the plugin created.

One of the bigger tasks is to get Twenty Twenty-Five committed, so the team working on that is pretty focused this week. It would be very valuable if people could take some time to test the theme and log any issues, create PRs (if able to), etc. To do so, visit https://github.com/WordPress/twentytwentyfive. There are instructions in the repo explaining how to set it up and get it running.

Next maintenance release

There are no maintenance releases planned at this time.

Next Gutenberg release: 19.3

The next Gutenberg release will be 19.3, scheduled for September 25, and will include the following issues.

Discussion

There were no discussion topics raised this week.

Open Floor

Cory Hughart shared that during 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/. at WCUS, the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Fields table spent the day diving through bleeding-edge Gutenberg code related to the new DataViews in posts and pages areas of the site editor. @sc0ttkclark is working on a dev blogblog (versus network, site) post, but the TL;DR is that we want to add some options to register_meta functions in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher to enable quick edit for custom fields. We’ll be talking more about it in the days ahead in #core-fields.

We finished Dev Chat by reviewing the tickets in the 6.7 milestone marked early.

Props to @mikachan for proofreading.

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

Joe McGill 12:40 am on September 13, 2024
Tags: 6-7, , ,   

Summary, Dev Chat, September 11, 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

WordPress 6.2.2 was released 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 can be found here.

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

Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.

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 (this release occurred after the meeting).

Discussion

@peterwilsoncc requested that we discuss the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Bindings UIUI User interface feature, 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. #61945.

To summarize his concern:

My main concern here is that the approach is to hide the UI from users with low permissions. I don’t feel that this is a great approach to handling a UI that is considered too technical, as I don’t think there is anything to suggest that an administrator will understand what an author does not.

So I’m of the view the interface ought to be improved and made less technical before it’s shipped in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@noisysocks suggested waiting on an update from Mario Santos, who is working on the feature, but added:

I’d be fine with just updating this to use caps. The interface doesn’t strike me as being too technical. Can put it in the Advanced tab if we’re worried…

…The short of it is that I’m okay with fixing the cap issue (add a new cap, don’t check against a role) and shipping in 6.7 or leaving it in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for more testing. Up to the team working on it. We have until beta 1 to decide.

@joemcgill highlighted two additional Slack updates this week:

Open Floor

@mikachan provided an update on #61708 on the agenda:

I’ve addressed the feedback by adding a deprecation notice to the pattern rather than removing it. I’d appreciate any thoughts on if this feels like a better approach.

@peterwilsoncc agreed to review.

@joemcgill pointed out #62004. @jrf recently asked all committers to review in full here. Julia shared the following updates during the meeting:

Ticket #53010 is basically the first step: splitting up the huge test classes to smaller classes which each only test one thing, i.e. one global function, one method in a class etc.

This includes making sure that the new test files comply with the PHPUnit naming conventions.

There are a number of patches attached to the ticket which can be used to see how to do this (mind: not all have been reviewed yet for the latest info).

I also think it would be great if we could get a decision on yes/no namespacing the test classes. I believe we should and that now is the time.

And followed up with

The other thing which would really really help, is to make sure that any new tests go in “clean”. As in: comply with the requirements for newer PHPUnit versions. The task is large enough as it is without having to clean up after new commits.

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

Sarah Norris 2:11 am on September 5, 2024
Tags: 6-7, , ,   

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: 6-7, , ,   

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