This post summarizes the weekly dev chat meeting from January 23rd (agenda, Slack archive).
5.1 updates
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. 2
5.1 beta 2 went out earlier this week.
There are a few tickets still open, most of them are related to fine tuning the WSOD handling.
Schedule update
Beta 3 is scheduled for January 29, this is also the soft string freeze. All string changes must be committed by then (except for the About page).
See also: WordPress 5.1 Development Cycle
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. status report
5.1 is being accompanied by a nice collection of dev notes, mainly from Make/Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. but also from Make/Polyglots.
@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to construct a 5.1 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. that summarizes collects all dev notes.
Updates from focus reps and component maintainers
Meeting notes and summaries
Other calls/proposals
Open floor
The 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/ Team is looking for more pull request reviewers. If you’re interested, please touch base with them in the #core-editor 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/. channel. Details to be shared soon in a Make/Core Post.
About including recent Gutenberg changes in the currently scheduled release: the WordPress 5.1 cycle is being a bit stricter about non-regression 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. 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 landing during the beta period, but WordPress 5.2 is expected to be able to take bug fixes during the WordPress beta period.
About the recent Post concerning the bulk edit process: many relevant opinions and thoughts were shared during the meeting.
- @matt expressed a desire to reopen the tickets closed in the recent bulk edit.
- @desrosj and @jeffpaul will work on a strategy for reverting closed tickets that have not been changed since the bulk edit, to allow the tickets to be properly evaluated for closure.
- Component maintainers to review related tickets (via this custom query). However, the 5.1 release is probably going to delay the ability to do that.
- Contributors can also use this Trac report (replacing “myusername” with their username and scrolling to those updated on January 4th) to find the tickets they have been involved with that were affected by the bulk closing.
- A
stale keyword and/or status was discussed as a good way to leave tickets open long term and avoid closing them as wontfix and maybelaterstatuses. - A post on Make/Core is coming next week to kick off the efforts of the new Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Team.
This Dev Chat Summary post is open for further comments and discussions.
#5-1, #dev-chat
