Please note Dev Chat is suspended on December 24th and January 1st 2020. It will be back on January 8th 2020, same time, same place!
The chat was facilitated by @francina on this agenda.
All the discussions can be found in Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel 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/. here.
Announcements and highlighted posts
@audrasjb gave an update about 5.3.1 version that was released on December 13. Right after, a couple of high severity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. issues were raised on Core Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. The release team then planned and held two 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. scrubs and released a provisional schedule for 5.3.2.
The first Release Candidate for 5.3.2 was released on December 17, with the 5 main issues fixed.
Update: WordPress 5.3.2 went live later yesterday after the devchat.
@francina gave a quick update of WordPress 5.4, which is ETA is still March 31 as initially planned. She is currently collecting feedback from component maintainers and the release could eventually be shortened if there are no big features planned to ship into the version.
@johnbillion precised that component maintainership doesn’t mean having to fix all the bugs, and that it’s more a shepherding role. So, anyone interested in maintaining a component or just wanting to know more is welcome to ping 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 committer 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. or release lead The community member ultimately responsible for the Release..
@imath called for attention on #33717 from the Comments component to which he proposed 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..
@francina then manifested her desire to see the Comments components as one of the focus for 5.4, since it has been abandoned for a while.
An interesting discussion about components and components maintainers then took place. @francina asked about how the Core team can help with the recruitment of maintainers.
@karmatosed suggested a few steps that would basically consist in
- Clarifying what component maintainers do.
- Being ok with people going in and out of that role, almost encouraging it to spread good people around.
- Looking at what is a focus for this coming year.
@garrett-eclipse suggested we do on Make/Core on seeking maintainers. He also proposed we can see who the regular contributors are in the component and reach out to them specifically.
@mikerbg said that a good step would be to identify individuals that are willing and able to provide some assistance to the marketing team to publicize recruitment opportunities and needs.
@jeremyfelt reminded this discussion from a chat in May, that it might worth looking at.
The full transcript of the discussions about components and components maintainers can be found here.