@marybaum and @metalandcoffee led the weekly meetings of the WordPress Core 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
- What’s new in Gutenberg 9.9? (5 February)
- A Week in Core – February 8, 2021
- WP Notify Planning Meeting Notes from Monday, February 8, 2021, with a call for contributors: “We invite all designers, developers, documentation writers, project managers, testers, builders, butchers, bakers, candlestick makers, and any other interested parties to join us and help build the WP Notify notifications system for WordPress”. Please reach out to @psykro (@jon_bossenger on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.) is you’re interested.
- 2021 Daylight Savings Time Planning
- WP 5.7 Dev 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.: Introducing new Post Parent related functions in WordPress 5.7
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 was released on February 3, 2021.
The minor 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 patch 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 ticket Created for both bug reports and feature development on the bug tracker. #52440.
WordPress 5.7 beta 2 was released on February 9, 2021.
@metalandcoffee: Beta 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.
Gutenberg 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 bug 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 notes 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 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 GitHub 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 plugin 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, I18N 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):
- There are some editor issues the editor team would like to draw attention to:
- Image block 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
WordPress 5.8 release squad:
- @poena would like to help if Full Site Editing and Twenty Twenty-One Blocks are included in this release
- Many people expressed their interest in being part of the release squad: @whyisjake, @boniu91, @nalininonstopnewsuk, @webcommsat, @marybaum, @sergeybiryukov, @audrasjb, @justinahinon, @metalandcoffee, @lukecarbis, @williampatton, @arpitgshah
- Everyone is welcome to comment this blogpost to show interest, or to get in touch with @francina or @davidbaumwald (@davidb on Slack) directly on Slack
- @jeffpaul is available to answer questions from non-engineer folks who are interested
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.”