Dev Chat Agenda: September 16th 2020


Here is the #agenda for this week’s meetings happening at: Wednesday, 16 September 2020, 0500UTC and Wednesday, 16 September 2020, 2000UTC

Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts
  1. i18n component bug scrub for WordPress 5.6: an 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. (internationalisation) focused 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 will be held tomorrow, Wednesday, September 16, 2020, 18:00 UTC in the #core channel on 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/.. It’s before dev-chat, it would be great to see many people there!
  • Calls from component maintainers and/or focus leads
  • Open Floor

    If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 16 September 2020, 05:00UTC and Wednesday, 16 September 2020, 2000UTC.

These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-6

Dev Chat Summary: (5.6 Week 4)

Greetings! Here’s what happened in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

0500 core devchat

@thewebprincess led the meeting and took notes. Find the full 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/. archive here.

2000 core devchat

@laurora led the chat; @thelmachido took notes. Here’s the full archive.

Both groups followed this agenda: https://make.wordpress.org/core/2020/09/08/dev-chat-agenda-september-9th-2020/

Announcements

We started by celebrating WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Ogijima in Japan over the weekend! 

@thewebprincess also highlighted a post by Shinichi Nishikawa about how they set up the tech and will share the link when she finds it.

Highlighted blogblog (versus network, site) posts

Timezones and Daylight savings:

After some discussion across timezones, the two dev chats have agreed to pin meeting times to UTC and let people adjust calendars locally. If the changes mean fewer people at meetings or involved in the project, several folks noted we can also change back.

The version 5.5 release team is still looking for feedback

Please share your perspective on the process — especially what people and teams can do to make future releases smoother for everyone. Please comment by Saturday at 8:00 UTC.

What’s next in Gutenberg

@annezazu updates the community once a month on all things 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.. It’s a great way to stay informed (planning your 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 or theme roadmap?) and get involved!

A comment on the agenda post:

 @pbearne asked for feedback this ticket. @peterwilsoncc answered and will give him  design feedback.

Component maintainers

Upgrade/Install 

Will explore adding some UIUI User interface elements to manage email notifications on plugin and theme auto-updates.

Privacy 

@carike reported in: “We have been receiving a lot of feedback, for which we are very grateful. Will update tickets over the next few days with more details on the proposed application design.” 

No updates of note this week from Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site, Options/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., Roles, Menus & Widgets, Build/Test Tools or Customize.

What if a component maintainer can’t make devchat?

After some discussion, this request from the group: Please add your updates as a comments on the Agenda post. 

Open Floor

@thewebprincess asked the people represented to call out the areas they’re focusing on. 
That morphed into a conversation about people’s desire to dig into contributing to E2E testing. At first, it looked imperative to wait for progress from the working group mentioned here – but the group decided there’s no real block to diving in now.

  • Should there be a 5.5.2? 
  •  Ever thought about being 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.? Here’s how you get there.
  • How can we help someone new — or even just watching from the sidelines —  find their place, or is it trial and error? See what people said in the full discussion.
  • One of those quizzes you get on social media all the time, “find your WordPress spirit animal”  led us to this tool, which the WCEU team used for contributor days. How could people use this — or a version — inside teams?

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

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

Dev Chat Agenda: September 9th 2020


Here is the #agenda for this week’s meetings happening at: Wednesday, 9 September 2020, 0500UTC and Wednesday, 9 September 2020, 2000UTC

Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts
  1. Core Chat – Timezones and Daylight savings – Action Required: Decision time – in relation to Daylight Saving adjustments, are we keeping the meeting time consistent with UTC? Or changing call times to stay consistent with calendar time?
  2. WordPress 5.5 Retrospective: We want to hear from you! – Action Required: Please add your response to the retrospective form with your thoughts from the 5.5 release – deadline Saturday September 12 07:00 UTC
  3. What’s next in Gutenberg (September): Comprehensive post about where things are at with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor – There may be action required of you are 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/theme dev, or if you want to get involved.
  • Calls from component maintainers and/or focus leads
  • Open Floor

    If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 2 September 2020, 05:00UTC and Wednesday, 9 September 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making 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/..

#5-6

Dev Chat Summary: (5.6 Week 3)

This post summarizes this week’s meetings happening on Wednesday, September 2, 2020, 07:00 AM GMT+2 and Wednesday, September 2, 2020, 10:00 PM GMT+2 on the agenda.

0500 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat

0500 Full meeting transcript on 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/.: https://wordpress.slack.com/archives/C02RQBWTW/p1599022834165200

@thewebprincess facilitated the meeting and took notes.

2000 core devchat

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack

Both groups followed the pre-prepared agenda and started the chat by acknowledging the adjustment to the new timing of the chat having moved it a day earlier.

Announcements

The group was excited about the release of version 5.5.1. @audrasjb thanked everyone who contributed to the release, specifically @winstina and @hauwaabashiya who hosted their first release parties.

Highlighted blogblog (versus network, site) posts

  • The discussion then turned to how best to accommodate Daylight Savings time changes – whether to shift the meeting or keep it at the UTC times which means time changes for participants.
    “ … how do we adjust for daylight savings?” see  @thewebprincess post. In recent years, the switch was made after all countries shifted to DST. What’s being proposed is that we switch that in favour of consistency with UTC. There’s a loosely described process on the matter in the handbook Daylight Saving Time (DST), however, given the more diverse geography attending dev chat, it may be time to reassess the process.
    We need to decide and document it in time for the first change due to take place on September 27 when NZ adjusts their clocks. The group agreed that the decision will be made next week in the meantime if you have something to add to help inform that decision, please leave comments on the post.

Then in the open time, two issues were discussed.

  • Then this issue https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/ was raised by @markparnell, asking the question ” what’s the feeling about this given the volume of jQuery issues after 5.5? are we ready to take the next step, or should we take things a little more slowly?” After some discussion, the conclusion was made that it’s too early yet for a decision and that timing of that point would be best before the 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. release (@pwcc) so the group will revisit in a couple of weeks. View slack archive.
    Afterwards, @timothyblynjacobs made a comment on the ticketticket Created for both bug reports and feature development on the bug tracker. “If we upgrade to jQuery 3.0 do we anticipate using any jQuery 3.0 features? Or if WordPress Core won’t be reliant on jQuery Migrate, … follow the conversation on Update jQuery step two ticket.
  • Awareness was raised on  Writing Developer Notes handbook for all contributors interested in writing dev-notes for future releases. Also, view the handbook on Leading Bug Scrubs that was based off a post during version 4.7 it was published recently.

Component maintainers

There is nothing of note from Build/Test Tools this week, but if anyone is interested in helping out with adding end to end / functional tests to the core then check out the post from a couple of weeks ago by @francina.

The Site Health team is assessing focuses for version 5.6 in their meeting next week.

@whyisjake – “While the release team is wrapping up the 5.5 processes, they want to reach out to the wider community for perspectives on the process and what could be done in the future to make releases smoother for everyone. Comments can be publicly shared directly on the post that is to come later, or as part of this form. All responses will be catalogued and then shared.”

Closing Remarks 

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/ 8.9 was released yesterday by @jorgefilipecosta! Of note, the new widgets screen was moved out of experimental. There will be more to come in the “What’s New” post for the release. A call for testing will be published on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ after some design changes are done.

@sergey This is for anyone working on unit tests in core, stricter type checking by using assertSame() should generally be preferred now to assertEquals() where appropriate, to make the tests more reliable. This is helpful in the ongoing work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support. See ticket for more details.

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 2, 2020, 10:00 PM GMT+2 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

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

Dev Chat Agenda: September 2nd 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday September 2nd 05:00 UTC and Wednesday September 2nd 20:00 UTC.

Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts 
  1. Deprecated JS globals – No action required, posting for awareness
  2. 5.5.1 – No action required, posting for awareness
  3. Core Chat – Timezones and Daylight savings – Request for comments please
  4. Bug Scrub Schedule No Action required: Posted for awareness
  • Calls from component maintainers
  • Open Floor

If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday September 2nd 05:00 UTC and Wednesday September 2nd20:00 UTC These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-6, #agenda, #dev-chat

Dev Chat Update – Timezones and Daylight Saving Time

Having discussed the following in both dev chat conversations last week this post is to bring you up to date with some small tweaks being made to bring both dev chat meetings into closer alignment.

The chat that happens at 0500UTC is more accessible to APAC region but has felt like it’s been appended to and has less weight than the 2000UTC meeting. After discussion last week in both meetings, the following changes are being made to balance that weight, and to also hopefully help encourage more participation in the newer meeting.

The 0500UTC chat will move 24hours earlier to Wednesday so both chats will fall on the same day.

That change has been reflected in the 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. here and in the Weekly Developer Chats page (the calendar update is in progress). Please reply in the comments below if there are any other areas in which this change needs to be updated (on the blogblog (versus network, site) or elsewhere).

This change clears the path to be able to refer to the dev chats by time rather than by region and hopefully removes blockers from anyone attending or wishing to attend who may have felt they were on the margins because they are based outside of APAC.

However, what is yet to be confirmed is how we respond to daylight saving changes. Whether the UTC timing of the chat shifts to stay consistent with local time (as it has done in the past), or whether the timing of the chat stays consistent with UTC and therefore changes locally when the clocks change.

The decision on this should be made before the next daylight saving changes take effect. The timeline for those changes is below in order they occur. Also noted is how keeping consistent with UTC will affect the timing of dev chat.

  • New Zealand – Sept 27 2020 – Later by 1 hour
  • Australia – October 4 2020 – Later by 1 hour
  • UK/EU – October 25 2020 – Earlier by 1 hour
  • US – November 1 2020 – Earlier by 1 hour

So, now here’s the question: Do we keep the time consistent with UTC? Or local time?

Props @peterwilsoncc for proofreading.

#apac, #dev-chat

Dev Chat Agenda for August 26, 2020

Here is the #agenda for this week’s meeting happening later today: Wednesday, August 26, 2020, 10:00 PM GMT+2. Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts 
  1. Discussion on the proposal to drop support for old PHP versions via a fixed schedule
  2. Request for Input: Consent Preferences for Logged In Users (Consent API)
  3. Request for comments on Dev Chat – APAC Edition Meeting Summary – August 20 2020
  4. Timing of release WordPress 5.5.1
  • Calls from component maintainers
  • Open Floor

If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat  meeting will be held on Wednesday, August 26, 2020, 10:00 PM GMT+2. This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

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

Dev Chat – APAC Edition Meeting Summary – August 20 2020

@peterwilsoncc called us to order and introduced @thewebprincess as the release coordinator and handed the chat over to her facilitation. 

The chat started out loosely following the same agenda as the earlier chat celebrating the commencement of the new release and release squad.

This sparked an excited response about having an APAC based release coordinator and a cheeky question about whether or not the release party would now fall into APAC timezones as a result. (Let’s cross that bridge when we come to it).

We also highlighted the same two posts for review.

Open floor

As it was initially a fairly quiet gathering @thewebprincess took the opportunity to ask some probing questions about what it’s like to contribute to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. when you’re based in the APAC timezones; specifically “What are the biggest challenges to contributing from this part of the world? And what more could be done to help alleviate those challenges?” 

There were some great responses to arise out of this conversation, which you can read in detail here

There was agreement that the advent of dev chat and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in APAC timezones have made the feeling of isolation from the core conversations has lessened somewhat which is great to hear.

The regional participants are also really hopeful that having release leadership based in this timezone will be a really positive step forward to increasing the cohort of participants in the region. 

We then discussed steps to help improve participation in the APAC region, these were the areas we covered:

  • @webcommsat advised that the marketing team have an initiative under way to help promote different meetings – so next steps is for a chat to happen to talk about what that might mean for APAC dev chat (and dev chat in general).
  • Making the APAC dev chat a bit more visible by taking and posting notes after the call (we have made a commitment to do this going forward, starting with these notes).
  • We then discussed the timing of the meeting and whether moving the APAC chat to before the Americas/EMEA one would help reduce barriers to entry for APAC participants (opening for discussion below).
  • Changing the language used to describe each dev chat in order to give them equal weight as a means to help increase participation/perceived value.

Requests for Comment

  1. The consensus for the members present was that there would be significant benefit in moving the APAC call forward (earlier) by 24 hours. This would mean:
  • The agenda notes would need to be posted 24 hours earlier than the APAC call to allow both discussions to follow similar agendas
  • There may be an increased need for maintainer teams to add their updates to the agenda post for discussion in the chats as most maintainers won’t be available for the earlier call
  1. Adjusting the language around how we describe the dev chats to give each equal weight – currently we have ‘dev chat’ and ‘APAC dev chat’ let’s discuss what a more equable format might look like… here are a couple of options that were thrown in to the call such as using UTC time to differentiate chats (2000UTC dev chat or 0500UTC dev chat), using regions – America/EMEA Dev Chat and APAC Dev Chat or something else…

What do you think?

Before making such changes it is important to open this up for discussion so that all interested/affected parties might add their thoughts to the conversation, we’d love to hear from you below if you have anything to contribute.

#5-6, #dev-chat, #summary

Dev Chat Meeting Summary – August 19, 2020

@thewebprincess facilitated the chat on this agenda.
Meeting recap by @laurora with @marybaum editing.

Full meeting transcript on Slack

Announcements

This meeting marked the official start of the 5.6 release – run by an all-woman team.

@yvettesonneveld summed it up: “Tonight we’re writing history!”

In another first for WordPress, @webcommsat said the 5.5 Question and Answers for Developers is in its final fact-checking.

Highlighted posts

Upcoming releases

WordPress 5.5.1

@audrasjb will run a 5.5.1 bugs scrub next Monday at 20:00 UTC.

Components check-in and status updates

@johnbillion  reminded the group that if you’re interested in helping maintain a component, whether active or not, feel free to speak up—to current maintainers, project leads or release leads.

AND if you’re a current maintainer who needs to step back for any reason, please feel free to do that at any time. Again, please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” a release or project lead. 

@jeffpaul flagged that for 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//editor-related items intending to ship in 5.6, it would be helpful to understand what may be needed from the other coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. component teams to ensure we have maintainers / committers / etc. ready to help.

An update on build/test tools from @jorbin: The top priority is #46149 — critical to support PHP8.

From Upgrade/Install, @whyisjake said he’s excited about the core auto-updates coming in #50907 and would love some feedback on getting started.

The Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site team has no firm plans for 5.6, but @johnbillion would like to reboot weekly chats again and carry on with the mini roadmap that started with default 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. values landing in 5.5.

On themes, @williampatton shared that the main goal this release cycle was to help unblock anything that #core-editor hits snags with.

@francina pointed out that the plan for 5.6 calls for a new default theme—ideally, one that starts to showcase 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. editor in template parts outside the_content.

Open floor

5.5.1

@joostdevalk raised 5.5.1 timing, since #50999 has unleashed a heavy support burden on his team.

The group supported a faster 5.5.1 release; there will be 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 on Friday and Monday, after which the team will make more concrete plans.

See the full discussion here.

Top Comments 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

@francina shared a plugin used on the Community Team blogblog (versus network, site) called ‘Top Comment’. It adds a final comment that recaps all the other comments in a discussion—a handy way to summarize discussions that have been going on a while.

#5-6#5-5-1#dev-chat#summary

#5-5-1, #5-6, #dev-chat

Dev Chat Summary, August 12th, 2020

@whyisjake hosted this agenda and @marybaum edited.

Component check-in and status updates

  • End-to-end testing
    • @whyisjake opened the chat by sharing @francina‘s post on E2E testing. She’s looking for feedback and would like to see more of that testing in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

  • 5.5 has landed! The release happened yesterday, on August 11, 2020.
    • @whyisjake thanked 800-plus contributors that made it, in his view, the greatest release of WordPress ever
  • 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. discussed 5.5 focal points and areas for improvement
    • @whyisjake and @marybaum addressed the enduring struggle to sync the about.php page with translators, when the squad often doesn’t get late-breaking info around the jazzer until the very last minute.
    • @audrasjb and @desrosj discussed a 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. with the placeholder video and inline image editing tools
    • @whyisjake began a lively conversation on the impact jQuery Migrate had on 5.5 planning with @jorbin, @ipstenu, @corinth, and @johnbillion. @Helen expressed a desire for clear messaging and more developer outreach on the topic, @jorbin noted that the marketing lead for future releases could increase awareness, and @marybaum, @webcommsat, and @annezazu discussed existing and planned marketing efforts.

Upcoming Releases

  • 5.5.1 release
    • @davidbaumwald offered to lead the 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.. @audrasjb, @johnbillion, @desrosj, @sergeybiryukov, @whyisjake, @azhiyadev, and @planningwrite and several others will join him. If you are interested in being part of the 5.5.1 release team, please note your interest in this post.
  • 5.6 release kickoff meeting will be August 19th during dev chat.

Open Floor

The next Core dev chat will be on Wednesday August 19, 2020 at 20:00 UTC

These meetings are held in the #core channel in the Making WordPress Core Slack instance.

Props to @audrasjb for review.

#5-5, #dev-chat