Dev Chat summary, November 9, 2022

The weekly WordPress developers chat meeting was held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at at 20:00 UTC.

Start of the meeting in Slack.

1.Welcome everyone

For anyone new to dev chat, you can find out more about this weekly meeting in the handbook.

The Dev Chat summary by @webcommsat and review by @pbiron and @audrasjb.

Agenda preparation – thanks to @webcommsat and @nalininonstopnewsuk for stepping in.

Meeting facilitators: @webcommsat and @desrosj, with @jeffpaul covering 6.1.1

2. Announcements

Reminder: WordPress 6.1 “Misha” was released, November 1, 2022

There is also now a 6.1 retrospective post – thanks @priethor

What’s new in Gutenberg 14.5 release post, November 9, 2022

3. Blogblog (versus network, site) posts

A Week in Core – November 7, 2022 – thanks to @audrasjb

No other blog posts were shared.

@webcommsat: a plug from the work from marketing, please do share social media posts from accounts. Social posts about the release continue to be very popular. If you are interested in stats, check out the marketing team’s blog as the notes report on this weekly.

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. nominations and elections 2023

@webcommsat highlighted that teams are starting to think about team rep elections for 2023. More on this in future meetings from the current team reps @marybaum and @audrasjb. @chanthaboune is also planning to write a post on the Make/ Updates blog on team rep elections in the project, and has said teams that have a robust nomination process can get started for 2023. @jeffpaul offered to help with the nominations and elections process in core from his previous experience.

To keep this in people’s awareness and as encouragement to contributors, the team rep nominations will be on the agenda for future dev chats in the run up to the elections for 2023. Once the nomination post in published, contributors can self-nominate or nominate anyone they think would be good in this role. The post will be shared in dev chat. If people are potentially interested, they can also chat with @marybaum or @audrasjb before adding a nomination to the public post. The election list will be posted on the core blog, but as part of the process, there will be a confirmation check with anyone nominated to make sure they are happy to stand.

Background: Team Reps and what they do in the project; 2022 process for Core Team Rep nominations

Discussion followed on whether a core team rep needed to be 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.. It was confirmed that it was not a requirement. @desrosj, and confirmed by …, “Honestly, it may be nice for both to not be a committer so that less coordination work falls on the shoulders of committers, and they have more free time to perform code reviews and commit duties. But being a committer also doesn’t disqualify you.”

4. Forthcoming releases

For those new to dev chat, this is where any updates on the releases are shared.

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.

Check out the 6.1 retrospective post – thanks @priethor.

@desrosj: All feedback and perspectives are welcome! Even if you were a casual contributor during the cycle, please do pass along your thoughts.

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

WordPress 6.1.1 Planning is live.

  • Editor sync to core for tomorrow, November 10, 2022
  • 6.1.1 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 is scheduled for tomorrow, November 10, 2022 at 17:30 UTC
  • 6.1.1 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). planned for Friday November 11, 2022 at 16:00 UTC
  • plan for 6.1.1 release on November 15, 2022. The release party will start at 17:00 UTC and aim to be ready for testing of the minor release package around 18:00 UTC

These will both take place in the core channel of the Make WordPress Slack.

Everyone welcome to help. @jeffpaul do you have anything to add on 6.1.1

Call for help: @jeffpaul encouraged people to help test and provide feedback, assist with patches/PRs, and/or help with commits on items in 6.1.1.

Later in the meeting, @desrosj shared there are 21 tickets currently in the workflow for 6.1. Tomorrow (November 10), @jeffpaul and @desrosj will be ‘heavy handed punting’ these tickets.
Action: They asked for any ticketticket Created for both bug reports and feature development on the bug tracker. to be updated which people felt strongly about making it in the time available for this release.

A question was raised on timings for the 6.1.1 release. The 6.1.1 planning post helps with this and is currently pinned to the top of the core blog.

c) Next major: 6.2

The Development Cycle page is up on the core blog and will be updated as we move through the cycle.

No other updates on 6.2 at dev chat.

5. Component maintainers updates / tickets / requests for help

a) Components

For anyone new, there is a help / ticket update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

@sergeybiryukov: Build/Test Tools, Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week.

@webcommsat: About/ Help and Bulk/ Quick Edit components – weekly focus on this will resume next week due to illness in the group. We will also be joined by two contributors who are interested in becoming maintainers or helping more with components. Timezones to enable this are being looked at.

b) Tickets

Action: @costdev requested if anyone is familiar with setting up WordPress to use FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website., testing on #56966 would be much appreciated. There is a detailed and very helpful testing note is on the ticket.

#56966: Updating plugins with WP6.1 creates .maintenance file and leaves it

No other tickets raised nor added to the agenda.

6) Open Floor

@costdev asked if the 6.1.1 release party could be held at 18:00 UTC rather than the planned 17:00 UTC as there were a lot of clashes with the Upgrade/Install component meeting during 6.1. The move would reduce disruption and mean the Upgrade/Install team could join for testing releases. They had to regularly skip the component meetings which are at 17:00 UTC to make sure the release was installing correctly.

Action: Agreed time change. Final party will still start at 17:00 UTC but the packaging and testing will move to around 18:00 UTC. @jeffpaul to update the Make/Core post timeline.

Props to: @webcommsat and @desrosj for running dev chat, @webcommsat for the summary, and to @jeffpaul and @costdev for review.

#6-1, #6-1-1, #dev-chat, #summary