This post is a summary of the latest dev chat meeting which took place on March 28th (agenda– Slack archive).
4.9.5 Release Candidate has been released Tuesday, 27th March.
The release candidate package is now ready for testing. Please help us by testing this release to ensure 4.9.5 fixes the reported issues and doesn’t introduce any new ones. 4.9.5 contains 25 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 and enhancements.
Please note: the "Try 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/" callout will probably land in 4.9.6, but not in 4.9.5. There are still a few Gutenberg issues that need to be fixed before it's ready for the amount of attention this will bring.
4.9.5 release following on Tuesday, April 3rd.
@danieltj, @audrasjb & @sergey to get in touch with concerned people (mission control, bundled themes & bundled plugins maintainers…) about 48 hours before the release.
Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. component maintainers
@jbpaul17 (jeffpaul 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 currently auditing component maintainers to make sure all components have a maintainer and in case anyone wishes to step down.
More accurately, there will be a call out to current component maintainers to nominate additional maintainers as they’re most aware of who’s contributing and able to help maintain a component.
From the build/test-tools component: new version of grunt-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.-wordpress was released and added to trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. Update your NPM modules. (see related post).
Feeds component: @stevenkword to ask for 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. having interest in that component to avoid getting stuck at the commit point and release leads to punt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) tickets to next release. @sergeybiryukov to help to look at any tickets in that component to get them to commitable state or figure out the next step. Any help welcome.
Note: if you are interested in becoming a component maintainer, please get in touch with current component mainteners first.
List of current component maintainers: https://make.wordpress.org/core/components/
Basically, component mainteners should:
- keep in mind that being a component maintainer means to be really well versed and know a lot (not necessarily everything) about that component.
- to care about it, but doesn’t have to be a developer: designers can maintain components. Ideally, there should be at least one designer for each component that touch UI User interface.
The new contributor meeting will also move it’s time in tandem with the dev chat. The next one is scheduled for next week, Tuesday at 19:00 UTC.