Tag Archives: summary

Jonathan Desrosiers 9:02 pm on February 24, 2021
Tags: , , , summary   

Dev Chat Summary: February 24, 2021

This post summarizes the weekly dev chat meeting from February 24, 2021 (Slack Archive). There was no APAC timed dev chat this week.

Announcements

WordPress 5.6.2 was released on Monday, February 22, 2021.

WordPress 5.6.2 Maintenance Release

WordPress 5.7 RC1 is also available for testing!

WordPress 5.7 Release Candidate

5.7 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. & developer notes

The WordPress 5.7 Field Guide has been published! All developer notes for the 5.7 release are included. Head on over and dive in!

WordPress 5.7 Field Guide

All 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. related to the 5.7 release can also be found by browsing the 5.7 and dev notes tags. Props to @audrasjb for making sure every ticketticket Created for both bug reports and feature development on the bug tracker. needing 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. had a guardian.

Blogblog (versus network, site) post highlights

Component maintainer updates

  • Build/Test Tools: @sergeybiryukov shared #33043, #52643.
  • Upgrade/Install: @audrasjb reiterated the call for feedback on the Rollback Plugin Update Feature Plugin post.
  • Date/Time: No major news to share this week.
  • General: No major news to share this week.
  • 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.: No major news to share this week.
  • Permalinks: No major news to share this week.
  • Menu/Widgets: No major news to share this week.

Open floor

  • @davidbaumwald proposed adding an officially recognized needs-testing-info keyword to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that can be used to request better documented steps for testing a proposed patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. The Meta-#5634 ticket has been opened to field feedback.

Next week

The next dev chat meetings will take place on Wednesday, March 3rd, 2021 at 5:00 UTC and Wednesday, March 3rd, 2021 at 20:00 UTC in the #core 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/. channel.

Props @hellofromtonya, @cbringmann, and @audrasjb for proof reading.

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

Nalini Thakor 6:41 pm on February 18, 2021
Tags: , , , summary   

Dev chat Meeting Summary: 17 Feb 2021

Full meeting on Make WordPress 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/.

Main discussions from 05:00 meeting:

  • @afragen: the Rollback Update Failure repo (here)
  • @tellthemachines: CSSCSS Cascading Style Sheets. themed 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 in #core-css (here)

Announcements

5.7 -related

  • 5.7 Beta 3 is here! Thanks you for testing, and to all the awesome people who have been tirelessly working on making WordPress happen—even going into this second year of pandemic.
  • WordPress 5.7 Docs Focus update: @audrasjb
    • Several 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. are just about ready, pending final review from component maintainers or by the corresponding ticketticket Created for both bug reports and feature development on the bug tracker. authors.
    • A list of the HelpHub pages that need updates once 5.7 launches.
    • If you worked on a ticket labelled needs-dev-note, or if you want to work on a devnotedev 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., please get in touch with @audrasjb to keep everything coordinated. (Ed. note: And the release squad knows where to send your props!)
  • 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. is still planned for RC1 next week. Co-ordinating with component maintainers taking place.

Minor releases

WordPress 5.6.2. RC 1 now available – @desrosj 5.6.2 

  • This one is a very small release, and the majority of the bug testing could be done in 10-15 minutes.
  • Additional testing available, raise tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets if any issues found. Focus to continue on 5.7
  • 5.6.2 will be pushed out on Monday 22 February 2021.
  • Aim is to try out a much smaller 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., which fixes a small handful of user-facing bugs that were finished and ready to go.
  • If it’s received well, we could potentially explore more frequent, smaller minor releases.
  • If you have any feedback around that, please feel free to share with @chanthaboune, @desrosj, or one of the Core team reps.

What’s new in 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/ 10.0.0

  • Version 10.0 is here!
  • It landed on 17 February 2021 and marks 100 releases of Gutenberg.
  • Congratulations to the Gutenberg team and all contributors involved.

Highlighted posts

Here are the latest 5.7 dev notes: 

Core editor front:

Full Site Editing:

  • work is going strong. Test, give feedback, ask friends to try it if they have never seen WP before and write down (with their consent of course) how they interact with the UIUI User interface, how does the UXUX User experience feels, etc.
  • @annezazu: The #fse-outreach-experiment needs you, no matter what you do with WordPress. The next call for testing will likely be this week, alongside a comprehensive update that follows the open submission for questions related to FSE.
  • If you want to test now, use this “How to Test” handbook page for FSE testing, and please share your feedback. (Though you don’t have to!)
  • Discussion: how to get more people sending feedback and asking questions, especially from people who do not follow the Core blogs.
    • @francina: raised questions on how to get more part, particularly students and meetups
    • @webcommsat: In Marketing, we are also helping non-tech users understand better what is happening on FSE and the benefits it will bring. This will help with future marcomms too. If anyone from a non tech background would like to add to the discussion session from this week, contact the Marketing Slack for the documents. We also work with community on newsletters and social to Meetups.
    • @timothyblynjacobs: Should we consider doing another Core dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user./callout like was done for 5.0?
    • @nalininonstopnewsuk: request to let Marketing know please if this is planned at a future date to include in the schedule. 
    • @annezazu: Latest call for questions is closed, 47 questions received. There will be future rounds for open questions so we can continue to refine the general ‘reach’ going forward.
    • @lukecarbis: We’re starting to think about restarting meetups here in Australia, so maybe we could even do some in-person click-around testing, if there is a script.
    • Where is the best place to encourage outreach on this— #fse-outreach-experiment (not a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. channel) or somewhere else? @annezazu suggested #core-editor channel on Slack. @Clorith suggested FSE-outreach channel to get testing and feedback on the feature before it lands in core.
  • Discussion to continue after the meeting.
  • A Week in Core – February 15, 2021 
  • Making WordPress Releases Easier from @chanthaboune.

Updates from component maintainers

Build/Test Tools update – Updates shared by @sergeybiryukov

  • Single-and 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 PHPUnit test runs on 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/ Actions are now separate jobs so they run in parallel and finish faster. Total duration was ~26 minutes; now it finishes in ~16 minutes. Thanks @johnbillion. Ticket #52548: Run Multisite tests in parallel during CI for more details.
  • Work keeps going to add missing @covers tags to PHPUnit tests, for better tracking of coder coverage. Ticket #39265: Missing @covers in the comment blocks in PHPUnit tests for more details.

General: noindex robots 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. 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.) was added to search results, to keep search engines from indexing internal search results (and guard against reflected web spam attacks). Ticket #52457: WordPress vulnerable to search-reflected webspam for more details.

Date/Time, 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 

More from Build/Test Tools – @desrosj
The GitHub Action workflow files are now backported all the way through 3.7, to bring back automated testing for those branches if they need a security release. He will publish a post with the overall status of the work on 18 February. 

Upgrade/Install:

@fragen: Feature plugin Rollback Update Failure needs testing—just install and activate.

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 will create a zip of the current plugin/theme version in wp-content/updates/rollback. The first test: check whether or not the process uses too many server resources. Does it cause a server timeout? There’s a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to simulate a failure.

@audrasjb  shared major news: @afragen has joined us as component maintainer

General component news:

@francina: Has started reaching out to component maintainers, both to gauge the situation of features/tickets for 5.8 and check how many are active. Those who aren’t will be moved to an emeriti status, like the one used for committers, as Josepha illustrated in the post Committers, Maintainers, and Emeriti

Committers, Maintainers, and Emeriti

If you:

Open Floor 

@Eclev91: Raised ticket #43495: Use Semantic Versioning for releases and asked for it to be reopened. “I’ve reviewed the discussion that took place in Slack that prompted the ticket, which noted that because core is currently on a base-10 versioning system, new and ready-to-launch features like ServeHappy and GDPR were blocked behind Gutenberg development slated for 5.0 (the idea of a 4.10 to launch these features was unheard of and untested). I added my thoughts to the ticket outlining a variety of QOL improvements for both core development and core consumers (devs like myself who maintain many WP sites) that could be gained by moving to semantic versioning. I imagine folks with hosting companies working on automating updates would also have $.02 to add.” If anyone has feedback, please post it in the Trac ticket.

Testing instructions

  • @justinahinon: a WordPress testing instructions document was drafted at the 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 Yoast (doc). Feedback about toning, phrasing, etc requested. Views on how it could work with the Core Handbook User Testing guide.
  • @jeffpaul: suggested a potential use could be in Make WordPress Test Handbook rather than the Core handbook .
  • @desrosj: this document is one that will be impossible to maintain over time. But it looks like each of the items you’ve detailed here so far look like great E2E test cases!
    • Some of these use cases could be used for user testing at meetups, or any other group of people that want to work on something together.
    • The steps change far too often release to release, and unless someone owns updating this document (or page) with each release, it will quickly become outdated. But if each of these are a test case, then they will fail when changes occur.
    • Not trying to discount having a document for testing at all! But feel this is far too detailed/intricate to maintain effectively for that purpose. 
    • @justinahinon: But if each of these are a test case, then they will fail when changes occur.

Growing Make Test Team

  • @francina: Interest in reviving the Test Team. It has been dormant for a while: no team reps, no chats.
  • During 5.6, @monikarao and others started weekly test scrubs.
  • @jeffpaul: queried whether weekly test scrubs were enough to consider people as leading the Test Team into action again. Worth encouraging.
  • Discussion: agreed.
  • @Desroj: Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. team actually falls under the Test team’s umbrella now. Results of that team’s efforts are usually posted to each individual ticket as we go through them. But that is just one form of testing.
  • We have a group of dedicated people showing up every week and that is amazing. At least one person on the team scrubs tickets present on a nearly daily basis.
  • @nalininonstopnewsuk: we are planning a promote a team every month idea in marketing. If you decide to put a plea out for testing team, let us know to feature it in the schedule. Agreed.

Thanks to @nalininonstopnewsuk, @webcommsat. and @marybaum for the dev-notes this week.

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

Jb Audras 11:18 pm on February 10, 2021
Tags: , , , summary   

DevChat meeting Summary – February 10, 2021

@marybaum and @metalandcoffee led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements and news

Amongst other news, there is one interesting news to share: according to W3Techs, 40% of the web uses WordPress 💥

As said in the W3Techs blogpost, “The incredible success story of WordPress continues by reaching another milestone: 2 out of every 5 websites use it now.”

Upcoming WordPress releases

WordPress 5.6.1

WordPress 5.6.1 was released on February 3, 2021.

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. squad plans to release a quick 5.6.2 after some issues were discovered with Classic Editor. A patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is being worked on in ticketticket Created for both bug reports and feature development on the bug tracker. #52440.

WordPress 5.7

WordPress 5.7 beta 2 was released on February 9, 2021.

@metalandcoffee: 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. 3 is next, then RC1, RC2 and finale release.

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/ 9.9 was released last week! It’s the final release that will be included in 5.7 and contains some fun improvements and lots 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.

@melchoyce shared that the about page is in progress. The marketing team plan to work on the copy. @melchoyce asked to post the work-in-progress in ticket #52347.

@audrasjb started to work on 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. and to prepare 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.. The first one was published a couple hours before the devchat. He will now reach out to ticket owners and component maintainers to ensure we have everything in time for RC1. Also, he started to identify what HelpHub pages (documentation for end-users) will need to be updated. @clorith mentioned the FAQ & Troubleshooting page, which is going to be recommended to users when there’s been a fatal error on their website.

Component maintainers updates

Build/Test Tools (@sergeybiryukov):

  • Work has completed on upgrading older branches to run on NodeJS LTS (currently 14.x), and backporting the local Docker environment to them. These changes unblock the ability to move automated testing over to 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/ Actions. See tickets #52341, #48301, and #50401 for more details.
  • The WordPress Importer pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is now installed when installing the Docker-based local environment. See ticket #49720 for more details.

Thanks to @desrosj who is working on these tasks!

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 (@sergeybiryukov): No major news this week.

Customize (@dlh): #50781 has a new patch that could use review and testing.

Site Health (@clorith): Nothing new and exciting to report this week, lots of late-cycle ticket made it in though.

Upgrade/Install (@afragen & @audrasjb):

Editor (@noisysocks):

  • There are some editor issues the editor team would like to draw attention to:
    • Image 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.: Duplicate copies of media files created in library #25805
    • Cover: 9.8 does not migrate content position correctly #28656
    • Reusable block can’t be converted to a regular block #26421
    • Can’t paste text into editor on IE 11 #26988

Open floor

WordPress 5.8 release squad:

Discussion about Internet Explorer 11 support:

  • Global usage is now 1%
  • It might go up again though
  • Let’s discuss during next release cycle
  • Let’s prepare a Make/Core post to announce a potential end of support for IE 11

News from Training/Learn WP, by @webcommsat: “We are also continuing to work with Training and Learn WordPress about how we can bring all the extra information and resources post release together to support users, and looking forward to continuing to chat to Support and Docs too. This kind of working together is great and thanks to everyone who has been involved.”

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

marybaum 6:50 pm on January 22, 2021
Tags: , , , , , summary   

Dev chat summary: January 21, 2021

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team postponed the afternoon dev chat for 24 hours to get past the US presidential inauguration. @metalandcoffee, aka Ebonie Butler, led the meeting on this agenda.

Announcements and highlighted posts

@metalandcoffee brought the group’s attention to these items:

Ebonie also invited the group (and you, too, dear reader!) to stop by a 5.7 test scrub. There’s one every Friday at 13:30 UTC.

Releases

The Core team is busy with one minor and one 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.

WordPress 5.6.1

5.6.1 has a squad and is deciding on a date; here are the tickets for the milestone.

WordPress 5.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 lands on February 2. Here are the tickets in the milestone.

Per @hellofromtonya, aka Tonya Mork, noted there are 66 open features and enhancements that need committing or punting by Beta 1. (Ed. note: Beta 1 imposes a feature freeze on the release. After that, commits are 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. 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 imposes a string freeze, so Polyglots can finish translations before final release.)

Tonya had more to share about the milestone tickets. See the full discussion and consider pitching in on some tickets, especially, as @metalandcoffee pointed out, if there’s something you really want to see in the release.

Updates from component maintainers

@sergeybiryukov kicked off the updates with a general announcement that as of January 21, WordPress Core has more than 50,000 commits and thanked every past, present and future contributor.

Sergey also reported in for Polyglots, which added support for Austria to remove_accents() in #49967.

@audrasjb reported in that Menus has two tickets ready for commit. In Upgrade/Install, JB recognized @dd32, aka Dion Hulse, for his helpful insights on rollbacks.

In Design, @estelaris, aka Estela Rueda, asked for testing to review this Core color-change pull request, based on a discussion in the Design channel that was happening at the same time as devchat.

@xkon reported in from Privacy, saying he’s pretty sure they’ll be punting some tickets from 5.7 that need more iteration. The team also expects inputs from other teams, which happens a lot with privacy.

Agenda comments

jQuery UIUI User interface and #52163

Between standard reports and Open Floor, devchat takes up items people add to the comments on the Agenda post—and other items people specifically add.

That happened with a question @hellofromtonya had on ticketticket Created for both bug reports and feature development on the bug tracker. #52163, which is about updating jQuery UI and removing jQuery migrate. All of that is getting punted to 5.8, but at the moment there’s no firm timeline for the new jQuery UI release. Follow the discussion as it happened here.

Consolidating instructions for local dev environments

Across the WordPress Project you can find several sets of instructions that will walk you through setting up a local development environment for building WordPress sites, themes, and plugins; contributing to all of those things plus Core; and doing lots of different kinds of testing.

Those local-environment instructions vary widely in age, approach and tooling.

@paaljoachim has started a Meta ticket (as opposed to a normal ticket) to discuss consolidating those instructions and would very much like feedback, comments and people to brainstorm with.

So far, @desrosj and @hellofromtonya have offered help. But this is a big, complicated thing — so please pitch in!

WordPress Importers

@pento offers this proposal to modernize the WordPress Importers, complete with a slew of links.

As he told the group, “

There’s a lot to read, but I’d appreciate folks taking the time to go through it. :slightly_smiling_face:2:44Much of it is fairly sensible, but the last post in the series does contain a proposal for writing exporters for CMSes that don’t provide an export option, which is a departure from our usual approach.”

See the real-time discussion here.

Visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. tests

@isabel_brison has a pull request that sets up visual regression testing in Core. The TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket is #49606.

@francina raised the point that some hosts are starting to do visual regression. See that discussion here.

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

@metalandcoffee: “Daniel Richards wanted to let everyone know that work on the block-based Navigation screen has picked up again, and there’s a new channel for [it] ” — #feature-navigation-block-editor.

Here’s the GitHub project.

Thoughts on browser versions?

@desrosj would like some feedback on #52331: Consider using more precise browser versions for `browserslist`.

Open Floor

@sergeybiryukov reminded the group that Beta and RC releases used to come with a haiku. He wrote one for the 50,000th commit and would like Core to restart the tradition.

@metalandcoffee volunteered to do a haiku for Beta 1 and closed the chat.

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

Nalini Thakor 6:25 pm on January 7, 2021
Tags: , , , summary   

DevChat Meeting Summary: January 7, 2021

@thewebprincess and @webcommsat led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC.

Thanks to @nalininonstopnewsuk and @webcommsat for the notes.
Slack archive for the 20:00 UTC meeting.

Announcements

  1. WordPress 5.7 news

2. Workshop submissions and testing calls

  • Full Site editing update
  • Learn WordPress
    • Got a dev workshop, or thinking of designing one? Submit it to Learn WordPress. Here’s a great example on using tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., that is already there: https://learn.wordpress.org/workshops/.
    • Follow and share promotions for #LearnWP and Meetups on social media too @WordCamp, @WordPressEvents and LinkedIn.

3. Monthly and weekly updates/ bulletins

Updates from the Component Maintainers and Focus Leads

Component maintainers do really important work. More about components at https://make.wordpress.org/core/components/

  • Update from @sergey:
    • Build/Test Tools – These change the frequency of code coverage reporting. A change was made in [49931] to display a relatively accurate code coverage data at https://codecov.io/gh/WordPress/wordpress-develop on any given day of the week.
    • Some other changes include updating several NPM packages and simplifying Composer package caching
    • 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., Date/Time, Permalinks: No major news this week.
  • Update from @sarahricker on accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)
    • several Accessibility Team members volunteered to stay up to date with accessibility needs for each component/focus
    • if your component doesn’t connect with an Accessibility member soon, let the team know.

Open Floor

  • Update from @Sergey on 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:
    • After almost a month since WordPress 5.6, for some reason the Gutenberg plugin still shows “Tested up to: 5.5.3” in the Plugin Directory and “Untested with your version of WordPress” when searching from a WordPress 5.6 adminadmin (and super admin), leading to search results that are not exactly great: https://cldup.com/nmU8Bq64U1.png
    • Note how every other plugin is listed as “compatible with your version of WordPress…”, but Gutenberg is “untested”.
    • Could we have an established process for updating the “Tested up to” version for Gutenberg? Boosting exact slug/name matches for plugin search was previously discussed in #meta3327 and some other 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. tickets. Apparently it’s not something that can or should be done at this time, however making sure that the “Tested up to” version is accurate should give us better search results. Ticket #3327: Searching with exact plugin name has it on page 3 of results
  • Promoting guidance for updating plugins to related WordPress versions
    • @webcommsat: Marketing has heard from Meetups and contributor events on intro talks on plugins development or basic talks on installing plugins: uncertainty about how plugins show they update to the current version. Potential to further promote guidance and advice.
    • @audrasjb recommended the Plugin development FAQ

Goals for 2021

Tickets requesting feedback

#5-7, #devchat

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

Jb Audras 12:15 pm on December 31, 2020
Tags: , , , summary   

DevChat meeting Summary – December 30th, 2020

@lukecarbis and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC.

Announcements

The WordPress 5.7 Development Cycle has been posted. The core team is targeting a final release date of March 9, 2021. More information available on the milestone page.

@hellofromtonya published the incoming bug scrubs schedule for 5.7.

The FSE (Full Site Editing) Outreach Program has its first call for Testers, specifically designed to explore the interaction between the two editing experiences (post vs. template editing) to make sure it’s clear when users are editing each. If you’d like to help test and provide feedback, please comment on the related post.

Another Week in Core blogpost was published. Most of the tickets of that timeline relate to Twenty Twenty-One and Twenty Nineteen bundled themes. Core team reps added a new props section to highlight contributors who made their very first contribution to WordPress Core.

A weekly Gutenberg update was also published on Make/Core.

Twenty Twenty-One and Twenty-Nineteen bundled themes recently had version updates. @desrosj published a recap on Make/Core. Indeed, bundled themes can iterate independently from Core releases. Of course, WP Core next point 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. will ship these changes.

Upcoming WordPress releases

WordPress 5.7

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead @hellofromtonya shared some insights:

  • We’ve had 4 early scrubs in Dec: with one in APAC and the other for EMEA/AMER
  • Participation has been light due to the year end and holidays
  • In January, we’ll shift focus to early, high priority, features, and enhancements

And also TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. stats:

  • 200 tickets in the milestone
  • 33 closed tickets
  • 31 tickets marked early
  • 86 defects
  • 68 enhancements
  • 6 features
  • 18 tasks

200 tickets for a 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 quite light. @hellofromtonya will be looking for other opportunities as well as talking with component teams/maintainers to see if there are other tickets we might be able to land in the milestone. @sergeybiryukov pointed out that with 4 releases a year instead of the usual 3, it’s expected that the number of tickets in each could be a bit lower. 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 coming quickly. So the quantity of tickets needs to be balanced with time and capacity.

@hellofromtonya shared a link to tickets marked as early + needs-testing. Everyone is invited to test them and provide feedback.

WordPress 5.6.1

There is currently 49 tickets in milestone 5.6.1. 23 are already closed as fixed, mostly related to Bundled themes.

As WP 5.6.1 may probably be released around mid-January, it would be nice to schedule few 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 next week. Please get in touch with @audrasjb if you want to run a scrub. @marybaum, @metalandcoffee and @hellofromtonya raised their hands during the chat. An agenda will be published by the beginning of January.

Component maintainers updates

From @sergeybiryukov:

Build/Test Tools: Random unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. failures in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. 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 controller tests due to external HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. request timeouts should now be resolved with [49913].

General: A second pass was made at replacing Codex URLs with a corresponding HelpHub or DevHub article in [49912].

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., Date/Time, Permalinks: No major news this week.

From @afragen:

Upgrade/Install: If you have access to a resource poor, shared hosting server we could use your testing experience on #51857. Specifically the goal is to determine if there might be a timeout issue for the zipping/unzipping processes.

@pbiron proposed to move #51928 to milestone 5.6.1. The attendees agreed to prioritize this ticketticket Created for both bug reports and feature development on the bug tracker. to get it ready for 5.6.1 release mid-January. @davidbaumwald raised some concern about moving an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to 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. milestone and about making final decision during devchat. The ticket was changed from enhancement to blessed task as this is not an enhancement for end-users but mostly something related to 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/ Updates APIs. @audrasjb pointed out that changing the milestone and the type of a ticket is not a final decision. Final decision will be the commit action. @dd32 was also mentionned for final decision, as WP Lead Developer and Updates APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. maintainer.

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

Dee Teal 3:32 am on December 17, 2020
Tags: , , summary   

Dev Chat Summary Dec 16th 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 16, 2020, 05:00 UTC, and Wednesday, December 16, 2020, 20:00 UTC. Both chats followed this agenda.

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@laurora facilitated the meeting and @thelmachido took notes. Find the full Slack archive here.

Announcements

Reminder – State of the Word is today. Set your alarm for the time Thursday, Dec 17th, 2020 at 1600 UTC so you don’t miss it!!

The 5.6 retrospective has started! We’d love as many of you as possible to share your feedback with us via the form linked in this post

The Full Site Editing Outreach program is officially underway. It will start with the release of 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/ 9.6 around December 23rd with plenty of time to be involved. If interested in joining the fun, please head on over to #fse-outreach-experiment. There is a comprehensive status update on Site Editing, view the post from Matias.

@abhanonstopnewsuk would like to inform us that the questions and answers on the release have had some updates thanks to a number of comments from user experience, to further help non-technical users. These updates will be posted on 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/.

Highlighted Posts

Component maintainers and focus leads

Build/Test Tools
Work has continued on GitHub Actions in this ticketticket Created for both bug reports and feature development on the bug tracker. #50401. There are also 3 relevant commits to take note of. r49781 Disable GitHub Action workflow runs triggered on push for forks and mirrors. r49782  Use NodeJS 14 in GitHub Action workflows. r49783  Enable reporting of results to WordPress.org

Site Health
A small ticket for 5.6.1 came in today, so it’s looking manageable

@clorith pointed out that jQuery updates got flagged early

Comments Component
@imath updated the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on this ticket #33717, feedbacks welcome

@flixos90 is planning to commit iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading today #50756

Upgrade and Install
There is a plan to have error stats for 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 updates failures sent to dotorg #51928 in 5.7

Open Floor

  • @iandunn would like to get some broader feedback on #51966 – please review and leave comments on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • A question was raised during chat, does a theme upgrade require being tied to a core upgrade?. The issue was raised because of this ticket #52040 @audrasjb said that this issue can be fixed in a TT1 release because a theme upgrade doesn’t need to be tied to a core upgrade. You can follow the full conversation here.
  • Learn WordPress was launched yesterday and a big cross teams effort including contributors from community, training, marketing, polyglots, design, 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., core and more. There are some more fun promotions in store too. Social videos have been produced for the promotion of Learn WordPress. Here is an example, the team would like to encourage contributions in other languages.  They’re also exploring how to support older audiences to use WordPress through the resources on Learn WordPress. Any hands to help with this? 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.” @nalini 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/..
  • @annezazu worked to redo the core feature projects page. Project owners where contacted for the latest status, description/intro paragraphs where updated, core editor items where added, and inactive projects where hidden to make the page more focused.

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 23rd 2020, 05:00 UTC and Wednesday, December 23rd 2020, 20:00UTC 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. 

#props to @thelmachido for consolidating both sets of notes together prior to publishing.

#5-7, #summary

Laura Nelson 9:34 pm on December 10, 2020
Tags: , , , summary   

Dev Chat Summary: December 9 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 9, 2020, 05:00 UTC and Wednesday, December 9, 2020, 20:00 UTC.

05:00 UTC core dev chat

@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@francina & @johnbillion facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.

Announcements

WordPress 5.6 aka “Simone” was released yesterday (8 December 2020). The release squad was entirely made of people identifying as women and non-binary folx. You can read more about the release in this blog post. At the time of the meeting, @helen shared that it’s already exceeded 3 million downloads.

The annual State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. will be taking place Thursday 17 December at 1600 UTC. If you’d like to submit a question, the deadline is Friday 11 December! This post has more information.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:

@desrosj is continuing to work on 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/ Action workflows and backporting the local Docker environment to the remaining older branches.

@desrosj has been working one repo at a time to convert the Travis configurations to workflows. If you maintain any repositories under the WordPress GitHub organization and want to help with the transition, feel free to DM him.

Open Floor

@afragen requested some extra eyes on #51976. If you’re able to help out, please add your comments to the ticketticket Created for both bug reports and feature development on the bug tracker.. And also added that if you’re after a larger challenge to take a look at #51928, noting that patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. might need to be moved to #51857.

Next Dev Chat meetings

The next meetings will take place on Wednesday, December 16, 2020, 05:00 UTC and Wednesday, December 16, 2020, 20:00 UTC in the #core 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/. channel. Please feel free to drop in with any updates or questions.

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

Kira Schroder 6:29 pm on December 8, 2020
Tags: , , , , summary   

Dev Chat Summary – 2 December 2020

The meeting was facilitated by @peterwilsoncc and @thewebprincess while @mikeschroder and @johnbillion took notes. Full meeting transcript on Slack. Both groups followed this pre-prepared agenda.

Announcements

  • WordPress 5.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). 2 has been released!

Highlighted Posts

  • A Week in Core – November 23, 2020
  • What’s next in Gutenberg? The monthly report is out
  • Discussion: Update the updater
  • 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. are continue to be updated ready for final release, here’s the latest dev-notes.
  • Release cycle discussion post – we need your feedback!
  • WP Notify project review

Component maintainers and focus leads

@peterwilsoncc reminded everyone that these components are in need of maintainers:

If you’re wondering what being a maintainer involves, @markparnell linked this guide from @francina.

Open Floor

@noisysocks requested review on #51612, which aims to make the  render_block_data, pre_render_block and render_block_context filters run on nested blocks. The PR with the latest approach can be found here.

The 2000 UTC group discussed #51913 and #51918 which led into a general discussion about the level of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support in 5.6 and how to communicate it. @marybaum asked for clarity to ensure all the marketing messaging is accurate.

The current consensus is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is “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.-compatible”, which means 5.6 works on its own with PHP 8, but that any given site may not work due to the plugins and themes in use and that more defensive programming is needed in core.

Next Dev Chat Meeting

The next meetings will take place on December 9, 2020 at 0500UTC and December 9, 2020 at 2000UTC in the #core 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/. 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. 

Apologies

Apologies from @johnbillion for the late posting of this summary. The post sat in draft until today when I was reminded of it.

Onwards!

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

thelmachido a11n 5:47 pm on November 26, 2020
Tags: , , , , summary   

Dev Chat Summary – 25 November 2020

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack. Both groups followed the pre-prepared agenda

Highlighted Posts

  1.  A week in Core. Take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between November 16 and November 23, 2020
  2. On November 24 the Field Guide was updated with new  Dev notes
  3. WP release cycle. If you work for a company whose product is influenced by WordPress releases, you are encouraged to join the discussion about aligning the WP release cycle with industry standards
  4. 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 and themes developers releases depend on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so it’s important that extenders reply.
  5. With the 5.6 release scheduled for December 8th, let’s start planning for 5.7. What’s on your wish-list for version 5.7
  6. The marketing team are starting working on ‘the Month in WordPress in their weekly meeting, please reach out if you have any contributions to share.
  7. Last but not least, the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 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. is now published. Folks are reminded to continue testing PHP 8

Component maintainers and focus leads

 PHP 8 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. @sergeybiryukov advised that PHP 8.0 release is scheduled for November 26. The dev note does a great job summarizing the changes and challenges PHP 8.0 brings for WordPress core and plugin or theme authors, so give it a read. There are a few components without a maintainer, and some that could use more maintainer support, a challenge was raised to people to consider contributing in this way, it’s not as hard as you might be thinking! See the discussion here and pick a component to dive into.

Open Floor


The Marketing Team is working on a social media pack on version 5.6, if anyone would like to support this, please let @lmurillom or @abhanonstopnewsuk know. Follow the conversation on slack 

Questions and answers for version 5.6
Where uploaded yesterday on 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/. @abhanonstopnewsuk – “ l would like to thank everyone who has already helped with this from the release squad, core and marketing, and a big shout out to @vimes1984 and  @meher who have led these questions and answers work with me over the last month.”

There are a number of tickets coming in since 5.6 RC1. @hellofromtonya will be scheduling a pre-RC2 Scrub Scheduled: Nov 30th @ 1900 UTC and will drop tickets into #core channel over the next few days to escalate.

The theme/theme directory teams have two requests for feedback on the make blogblog (versus network, site), https://make.wordpress.org/themes/2020/11/18/theme-previews-in-the-time-of-blocks/ and https://make.wordpress.org/themes/2020/11/19/feedback-requested-resolution-process-for-issues-found-in-live-themes/  please review and add your thoughts.

Mike asked for more testing assistance with https://github.com/WordPress/phpunit-test-runner/issues/121 in the hopes we can get this across the line. Finally, Paal posted a note that he’s going to be focusing on improving the structure of the handbooks, watch this space to see how that develops

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 2, 2020, 07:00 AM GMT+2 and Wednesday, December 2, 2020, 10:00 PM GMT+2 in the #core 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/. 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-6, #5-7, #dev-chat, #summary