Dev Chat Summary: July 18, 2018 (4.9.8 Week 2)

Welcome!

The WordPress coreCore Core 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 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

This post summarizes the weekly devchat meeting held Wednesday, July 18, 2018 (agenda | Slack archive). I updated the date!

4.9.8 Update

The freshest of news from release leads @pbiron and @joshuawold, and deputies @sergeybiryukov and @psykro:

4.9.8 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. 1

4.9.8 Beta 1 was released Tuesday, July 17, 2018. It’s open for testing, so hop on these tickets.
Beta 1 includes an updated version of TinyMCE (4.8.0). It needs special attention, since it was not thoroughly vetted before the release. Here are the release notes and change log, so go forth and test!

4.9.8 Beta 2

Note: 4.9.8 Beta 2 was released as planned in the notes below. I am a monster and very late with the dev chat recap.

4.9.8 Beta 2 release scheduled for Thursday, July 19, 2018, with the goal of including the Try 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/ callout. There are some issues on the callout that need attention, so it may be reverted if necessary.
@kadamwhite back-ported r43510 for inclusion in Beta 2, as it may also help with Gutenberg metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. handling. It’s quite the cohesive Beta 2 release, as Tim Gunn would say.
Any other Beta 2 inclusions are listed here.

Focus Lead and Component Maintainer Updates

Two chat summaries for you to peruse:

Open Floor / Q&A

Question via @pbiron: If the privacy 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. fixes mentioned previously become ready, do we need to another beta for those or can they be included in RC without appearing in a Beta?

The consensus is that it’s best to do a Beta release for privacy bug fixes. However, @desrosj is out until Monday, so including these fixes in a Beta this Tuesday and delaying 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). to Thursday/Friday is probably not doable. The current plan is to keep the schedule below, and reevaluate the significance of the open privacy bugs with @desrosj upon his return:

Beta 2 – Thursday, July 19, 2018
RC – Tuesday, July 24, 2018
Final – Tuesday, July 31, 2018

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 25, 2018, 20:00:00 UTC in the #core 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/. 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.

Soren Wrede 12:18 pm on July 23, 2018

Wrong date in the title 😉
- whitneyyadrich 12:31 pm on July 23, 2018
  
  Derp. Updated. Thanks!
  
  https://media.giphy.com/media/rej07KlIYlax2/giphy.gif
adrian33000 3:42 pm on July 23, 2018

Hi
It seems there are clear instructions to retain the classic editor when 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/ launches in V5 later this year.

However, for anyone opting to do so there does not seem to be any advice provided as to how to then revert to Gutenberg after having defaulted to the classic editor.

I assume one would just delete the classic editor pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and Gutenberg as the then coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor would appear but it might be an idea to make this clear somewhere in the notices for those who might not understand the difference between a plugin and core features.

Comments are closed.