The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
Off-forum support requests – highlighted in the team reps group this week, this discussion is looking for awareness, discussion, and feedback
Proposal to stop merging experimental APIs from GutenbergGutenbergThe 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/ to WordPress core (August 10, 2022)
@annezazu shared this latest call for testing facilitators. It is an open call for anyone interested in being part of the actual creation of / facilitation of calls for testing to help scale WordPress efforts in this area
The Learn team is also looking for some new contributors. Would you like to help produce material about what’s new in each release? Please contact @Courtney@Pooja Derashri@Hauwa Abashiya or @abhanonstopnewsuk (Slack IDs) in #training. You’ll also have a chance to help with some other, related, collaborative opportunities.
4. Upcoming releases
a) Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.1
Bug scrub schedule for 6.1 now out – anyone can help out or observe and learn more about how to get involved with moving tickets forward.
As @marybaum and others have highlighted, anyone can volunteer to run a bugbugA 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. There’s helpful information in the Core Handbook to get you started. If you spot something that needs explaining further in the Handbook, do let the release squad or the Core reps know too.
Right now, the people who have volunteered to lead the minors are leaning towards Release Candidaterelease candidateOne 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). (RCrelease candidateOne 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).) on August 23 and final on August 30, 2022, pending confirmation with the security team.
Shared last week, link to the public discussion on Slack on 6.0.2. As soon as there are set dates, there will be updates in these Slack channels: #core, #core-editor, and #6-0-release-leads confirming.
@marybaum: If you’re new to the process and want to follow along, discussions about minors live in the release-leads channel of the major they are part of.
5. TicketticketCreated for both bug reports and feature development on the bug tracker. help / Component Maintainers requests
Build/Test Tools: An effort on adding missing @covers tags for WordPress unit testunit testCode 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 has continued. Ticket #39265 for more details.
Date/Time, General, I18Ni18nInternationalization, 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.
Help/ About component: @marybaum and I have been looking through tickets ready for a scrub next week. We started a ticket for the About Page so that it could be included in the milestone. I have set up the folders for images and the About Page materials ready.
Quick/ Bulk Editcomponent:@nalininonstopnewsuk and I have identified a number of tickets to be included in a scrub and prioritizing which ones to move forward based on patches etc.
For both components, we will be following up in the next few weeks with some of those who have been helping progress the the tickets.
Other component maintainers were encouraged to share their progress at Dev Chat or on the agendas, and as a good way of highlighting the component and if any help was needed.
If you are new to Dev Chat, you can find out more on the core blogabout components and who the maintainers are, as well as how you can volunteer.
joined as a maintainer for the Upgrade/Install component last night, and is looking forward to helping move tickets forward and improve the component. Congratulations!
b. Tickets to highlight for help
TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Ticket #56283 – @audrasjb has asked for attention on this ticket, pointing out that it needs a consensus.
Gutenberg Ticket #35852 – @mamaduka, and the core editor bug scrub from earlier today, would like further testing on this please.
6. Open Floor
No other items were raised.
The next Dev Chat will be on: Wednesday 17 August 2022, at 20:00 UTC .
Props to @webcommsat for the summary, and to @marybaum and @costdev for reviewing. Could you write next week’s summary?
