This post summarizes the weekly devchat meeting held Wednesday, July 11, 2018 (agenda | Slack archive)
4.9.7 Security and Maintenance Release Feedback
- WordPress 4.9.7 was released on Thursday, July 5 2018. This was a Maintenance & Security Release. Details here.
- All 4.9.7 milestone tickets were pushed to 4.9.8. The last devchat summary and some other posts on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. have been updated to replace “4.9.7” mentions with “4.9.8”
4.9.8 Release Leads
As confirmed last week:
- Release leads: @pbiron and @joshuawold
- Deputies: @sergeybiryukovand and @psykro
4.9.8 Schedule
- BetaBeta 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.: July 17, 2018
- RCrelease candidate One 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).: July 24, 2018
- Final Release: July 31, 2018
- Bug Scrubs: Monday at 14:00 UTC and Thursday at 21:30 UTC during the cycle.
4.9.8 Development Update
Updates from @pbiron:
- URGENT: Please help with these tickets (#42362, #44532) ASAP, as they’re leading to significant disruptions for users
- These tickets are marked ready for commit for 4.9.8
- These tickets are ready for 4.9.8 or backport to 4.9.8, but have not yet been officially committed
- #44133 likely needs to be resolved and approved by this weekend if it’s going to be included in 4.9.8
- Bug Scrub on Thursday, July 12, 2018 will cover:
- The URGENT tickets mentioned above
- As many of these tickets as possible
Focus Lead and Component Maintainer Updates
GutenbergGutenberg 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/
- We need ticket/issue gardeners to help with labeling. Find @designsimply (@sheri on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/) to help out.
- @designsimply could also use help bugbug 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. scrubbing. Find her in the in #core-editor or #core-test Slack channels.
- Here’s a whole list of issues you can test and it will be updated often
- Primary goal: Scrub the
[Type] Buglabel to check validity, verify labels, and close fixed/inactives. - And then: Focus on
no:labeland follow these steps
- Last week, the team released 3.2 with a hefty change log
- Please proceed as if the “Try Gutenberg” callout blockers (#7147) will be solved in time for inclusion in 4.9.8. If it’s not ready in time, we’ll pull it from the release.
JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.com
The JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. team posted notes on their meeting. Topics included:
- Deprecation Strategy
- WordPress package to be merged into Gutenberg
- Merging WordPress JavaScript coding standards in Gutenberg
- Service Workers scope
General Announcements
Devchat Coordination Reminder
Jeff Paul is on vacation, so @whitneyyadrich, @audrasjb, @joemcgill, and @antpb are handling PM-y devchat duties this month: collecting agenda items, publishing an agenda, running the actual devchat meeting, and publishing a devchat summary.
Next Meeting
The next meeting will take place on Wednesday, July 18, 2018, 20:00:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss, but cannot make the meeting, please leave a comment on this post so that we can take them into account.