Dev Chat agenda.
The meeting was led by @webcommsat and @marybaum.
Start of the Dev Chat meeting in the Make WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/..
You can find last week’s notes in at Dev chat summary, December 15, 2021.
Please join the discussion @chanthaboune has started on 2022 release planning.
WordPress 5.9 release updates
The WordPress 5.9 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. 4 has landed. Please download and test! Thanks to everyone who has been involved in the release so far and getting the Beta 4 out the door.
Beta 4 fixes 20 bugs that surfaced in Beta 3. Please test them and report your findings on the announcement post.
It does not look like a Beta 5 will be necessary at this stage. RC1 is scheduled for January 4, 2022. The revised 5.9 release schedule.
If there are no big issues, the release will continue to follow the plan from November 22, 2021 – more details on the 5.9 post.
Blog (versus network, site) posts to note
What’s new in Gutenberg 12.2? (December 22, 2021)
A Week in Core. Three new contributors to core this week – welcome to them all.
The next New Contributor Meeting for core is scheduled for 12 January 2022 at 19:00 UTC. If you have any questions on contributing to core before that, just bring them up here in #core any time outside of any ongoing meeting, or in the open floor section of the weekly dev chat, and someone should follow up.
Please continue to share the Help test WordPress 5.9 features. This replaces the ongoing call for FSE testing promotions until after 5.9 is released. Thanks @annezazu
WordPress 5.9 is now available for translation. The new theme with this release, Twenty Twenty-Two, can also be translated. Thanks to all the polyglots across the world who have started working on translating the next release.
The annual community survey closes next week on December 30, 2021. Still time to complete it.
Component Maintainers update
Update via @sergeybiryukov: Some enhancements were made to the unit 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. suite:
- Reduce the use of unnecessary randomness in tests to increase the overall reliability of the tests. See ticket Created for both bug reports and feature development on the bug tracker. #37371 for more details.
- Remove an assertion in filter_rest_url_for_leading_slash(). This assertion could mask the fact that some other tests don’t perform an assertion. See ticket #54661 for more details.
Thanks @johnbillion and @johnillo, a new contributor!
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
Update via @sergeybiryukov: No major news this week.
Quick/Bulk Edit component
Update from @nalininonstopnewsuk: For the Quick/ Bulk Edit component, we are continuing to work through and reading all the previous materials in the background while the primary focus is on 5.9. We want to run a 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. scrub on the tickets the week after 5.9 is out.
About / Help page component
Update via @webcommsat: More updates have been done this week on the text and Figma. Will update the ticket today.
You can also join the collaborations cross-team on social media posts on the release features.
- Proposal for an enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ticket.
@maksimkuzmin would like some comments on this message in Slack before Jan, 12?
Will raise a ticket and provide a UI User interface draft. Design input suggested.
Discussion suggested moving the ticket to 6.0.
2. Request to add thoughts on the Performance Team 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/ Issues and Projects.
@Sergio Scabuzzo from the measurement group in the team encouraged contributors to look at the ideas. https://github.com/WordPress/performance/projects
3. A second enhancement proposal
@maksimkuzmin suggested: Most of the times bespoke themes built relying on page templates to set up specific page to the specific type of page. E.g. Search Page is bound to the page-search.php template in the code. The major lack of functionality is to have a function that will quickly retrieve page(s) by the given template name. Without building a WP Query, etc. Sort of
get_page_by_template( $template_file ).
This enhancement will further be discussed and potentially reconsidered in a pre-existing ticket: #16264.
4. Bug report potentially related to 5.9
@afragen: FYI, posted bug report and PR for #54682, believed to be 5.9 related.
Dev Chat will take place next week, Wednesday 29 December 2021 at 20:00 UTC in the Make WordPress Core Slack for a quick check-in.
Props: Dev Chat summary by @webcommsat. Thanks to @marybaum and @sergey for proofing.