Dev Chat agenda, November 2, 2022

The meetings take place on Wednesdays at 20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.

About Dev Chat.

The publication of the Dev Chat agenda was held for the release party of WordPress 6.1to include the updates related to it.

1. Welcome

Introduction from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum

Dev Chat summary, October 27, 2022 – thanks to @webcommsat for writing it and for checking items for today’s agenda.

2. Announcements

WordPress 6.1 “Misha” was released, November 1, 2022
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/ 14.5 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). expected November 2, 2022

During the last week:
6.1 Release Candidate 6 – October 31, 2022

6.1 Release Candidate 5 – October 28, 2022

Gutenberg 14.4 was released –“What’s new in Gutenberg 14.4” release post, October 27, 2022.

3. Blogblog (versus network, site) posts of note

A Week in Core – October 31, 2022

Performance chat summary, November 1, 2022 – has some ticketticket Created for both bug reports and feature development on the bug tracker. updates including WebP, AVIF images, Object Cache. Also some calls for reviews.

Core editor improvement: enhancing the writing experience, October 28, 2022. Find more about other improvements to the core editor.

4. Forthcoming releases

Updates from the relevant teams relating to releases.

a) Latest 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.1

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 find them at the dev-notes-6-1 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field Guide for 6.1.

b) 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.1.1

c) Next major: 6.2

Is there an update on the discussion on earlies?

If you have an update from release leads or any teams collaborating on related items, please add a comment.

5. Component maintainers updates / tickets / requests for help

Please add your request for tickets you would like to raise as a comment.

6. Open Floor

Please add your Open Floor item as a comment.

Thanks to @marybaum for reviewing the agenda.

#6-1#agenda#dev-chat

#6-1, #6-1-1, #6-2, #agenda, #dev-chat

Dev Chat agenda, October 19, 2022

The meetings take place on Wednesdays at  20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.

About Dev Chat.

The publication of the Dev Chat agenda was held until after the WordPress 6.1 RC2 release party concluded to include the updates from this.

1. Welcome

Dev Chat summary, October 12, 2022 – thanks to @marybaum for writing it.

2. Announcements

WordPress 6.1 Release Candidate 2 is available to test.

What’s new in Gutenberg Plugin 14.3.

3. Blogblog (versus network, site) posts of note

New handbook from WordPress Core Performance.

4. Forthcoming releases

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 are in process, going through tech and editorial review, and published as they are ready. Find them at the dev-notes-6-1 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will be out shortly. Thanks to the efforts led by the release docs team.

WordPress 6.1 Release Candidate 1 is available to test.

Dev Notes relating to the 6.1 release.

If you have an update from release leads or any teams collaborating on related items, please add a comment.

5. Component maintainers updates / tickets / requests for help

Please add your request for tickets you would like to raise as a comment.

6. Open Floor

Please add your Open Floor item as a comment.

#6-1#agenda#dev-chat

#6-1, #agenda, #dev-chat

Dev Chat agenda, October 12, 2022

The meetings take place on Wednesdays at  20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.

About Dev Chat.

The publication of the Dev Chat agenda was held until after the WordPress 6.1 RC1 release party concluded to include the updates from this.

1. Welcome

Dev Chat summary, October 5, 2022 – thanks to @ndiego for writing, and @webcommsat and @marybaum for reviewing.

2. Announcements

WordPress 6.1 Release Candidate 1 is available to test.

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 14.3 is due to land on October 12. Its RC is already available.

3. Blogblog (versus network, site) posts of note

A Week in Core, August 10, 2022

4. Forthcoming releases

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 are in process, going through tech and editorial review, and published as they are ready. Find them at the dev-notes-6-1 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will be out shortly. Thanks to the efforts led by the release docs team.

WordPress 6.1 Release Candidate 1 is available to test.

Note 1: Double sign-off is needed for tickets with milestone 6.1, no matter 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. or 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"./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.. Note 2: Trunk was not branched on October 11, 2022 following RC1.

If you have an update from release leads or any teams collaborating on related items, please add a comment.

5. Component maintainers updates / tickets / requests for help

Please add your request for tickets you would like to raise as a comment.

6. Open Floor

Please add your Open Floor item as a comment.

#6-1, #agenda, #dev-chat

Dev Chat agenda, September 21, 2022

Additional information added to section 4 releases on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets requiring attention – update added September 21, @webcommsat.

The weekly WordPress Developers Chat will take place on Wednesday, September 21 2022 at 20:00 UTC .
All are welcome to join the chat in the #Core channel of 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/..

1. Welcome

2. Announcements

WordPress 6.1 Beta 1 release party will now be on Wednesday September 21, at approximately 16:00 UTC. Please note: the rest of the release schedule is unchanged.

What’s new in Gutenberg 14.1 – this is the last release that goes with WordPress 6.1.

3. Blogblog (versus network, site) posts

A week in core – published September 19, 2022

Releasing a new version of Twenty Twenty Two theme so that the accessibility ready label can be added. This is an important change and marks the first 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. theme with that label, opening the door for more people to be able to explore using various Full Site Editing (FSE) features.

Core performance team is reviewing its missions and philosophies – document can be found in its meeting summary for September 20, 2022.

Update on Dominant color feature, which has been highlighted in recent dev chats – discussion in the performance meeting.

Notes from Developer blog – first editorial meeting, September 1, 2022

4. Releases

The 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. is 6.1

a) Update from members of the release squad.

b) The following tickets have been highlighted by @jeffpaul for focus at the meeting for discussion especially on whether it should be reverted heading into 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 on Tuesday, September 27, 2022. Please check the tickets and add comments there. Tickets #56400 and #19898.

Any other updates from release squad and those working on 6.1?

c) Useful links
WordPress 6.1 Development cycle

Bug scrub schedule for 6.1

5. Component maintainers issues / help with ticketticket Created for both bug reports and feature development on the bug tracker. requests

Comments or asynchronous updates can be added to this agenda.

6. Open Floor

Comments or asynchronous updates can be added to this agenda.

#6-1, #agenda, #dev-chat

Agenda, Dev Chat, August 10, 2022

The weekly WordPress Developers Chat on Wednesdays at 20:00 UTC. This is the agenda for August 10, 2022. Please join the chat in the #Core channel of 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/.; the meeting is for everyone.

1. Welcome

Dev Chat summary, August 3, 2022

2. Announcements

3. Blogblog (versus network, site) posts

What’s new in Gutenberg 13.8 (August 3, 2022 post)

A Week in Core (August 8, 2022 post)

Giving FSE a more user-friendly name – this discussion post, from July 27, is still open.

Off-forum support requests – Highlighted in the team reps group this week, this discussion is looking for awareness, discussion, and feedback.

4. Upcoming releases

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

c) 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.0.2

5. Ticketticket Created for both bug reports and feature development on the bug tracker. help / Component Maintainers requests

If you are a component maintainer, this is your time to highlight a ticket or give an update. You can also add information in the comments section.

a) Component maintainers – any issues?

b) Tickets to raise?

Trac Ticket #56283: consensus needed (@audrasjb)

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/ Ticket #35852 – request from @mamaduka and the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor 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 for testing.

6. Open Floor

Do you have something for Open Floor? Please add it in the comments below.

#6-1, #agenda, #dev-chat

Dev chat agenda, June 29, 2022

1. Welcome

Last week’s summary

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

3. Blogblog (versus network, site) posts of note

A week in Core, June 27

4. Upcoming releases

The next major is WordPress 6.1.

If you have early tickets, announcements, or you need some help, there’s time here for you.

The next minor is WordPress 6.0.1.

@annezazu has published a team and a schedule!

5. Open floor

Component maintainers with reports have priority. Then, if you have an item, please add it to the comments. If you aren’t going to make the chat, please say so, and the facilitators will bring up your item. If you have a report, the group can post that for you too — again, if a facilitator knows about it.

#6-0-1, #6-1, #agenda

Dev chat agenda, June 22, 2022

The weekly meeting of the developers chat will be held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. at 20:00 UTC.

1. 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/ 13.5 lands Wednesday afternoon!

2. Blogblog (versus network, site) posts of note

A Week in Core, from @audrasjb

@matveb‘s post on the Admin experience

What’s new in Gutenberg 13.5? (link to come, since 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 lands Wednesday at about dev chat time)

Discussion: on disallow assignments in conditions and remove the Yoda condition requirement for PHP. This discussion started on the WordPress Coding Standards (WPCS) repo.

A roadmap to 6.1, also from @matveb

And a YouTube show on FSE and themes.

3. Upcoming releases

The next major is 6.1. @costdev is running early bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs: the schedule.

The next minor is 6.0.1. Some tasks for the editor.

4. Open Floor

Are you a component maintainer? Your report, or any ticketticket Created for both bug reports and feature development on the bug tracker. you need eyes on, comes before other items. Especially if you add a comment below!

After components and tickets, the floor is open. If you’re not going to be at the meeting, please say so in your comment, and the facilitators will bring up your item for you. Are there are areas you would like help with or tickets you wish to highlight.

Thanks to @webcommsat for contributing to this agenda.

#6-01, #6-1, #agenda, #core, #dev-chat

Dev Chat Agenda, June 15, 2022

In this post you will find the agenda for the weekly WordPress Developers Chat at June 15, 2022, at 20:00 UTC. All welcome to join the chat in the #Core channel of 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/..

1. Welcome

Dev Chat summary, June 8, 2022

2. Announcements

3. Blogblog (versus network, site) posts

What’s new in Gutenberg 13.4 (June 10, 2022 post)

A Week in Core – June 13, 2022

Discussion: on disallow assignments in conditions and remove the Yoda condition requirement for PHP. This continues the discussion on the WordPress Coding Standards (WPCS) repo.

4. Upcoming releases

a) WordPress 6.0 ‘Arturo’ Retrospective – the form is open until June 19, 2022

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

Early bug scrub schedule for 6.1

c) 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.0.1

6.0.1 Editor Tasks board

5. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.

The first of a number of sprints to help update the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Contributor Handbook will take place on Monday June 20, 2022, 20:00 UTC. All welcome.

A sprint will take place in July in APAC time, more dates to follow.

If you would like to assist with this or have a page of the handbook that you would like to focus on, please contact @marybaum and @webcommsat who are pulling together items for the sprints.

6. Open Floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

a) Component maintainers – any issues?

b) Tickets to raise?

c) Any other items?

#6-1, #agenda, #dev-chat