5.0 / Gutenberg Status Update – Nov 21

  • Open issues in 5.0 RC: 0 (=)
  • Open issues in 5.0.0: 20 (+2)
  • Open issues in 5.0.1: 29 (+11)
  • Open issues in 5.0.x (fast follow): 106 (+19)
  • Current beta: Beta 5, released November 15.
  • Current plugin: 4.5.1, released today.
  • Next release: 5.0 RC, planned for tomorrow (assuming issues below are resolved).

Current pending tasks for 5.0 RC are listed on trac, not on the Gutenberg repository. Going forward outstanding tasks in trac will be included in the updates for better visibility.

The date for 5.0 release is under consideration, given it’s not plausible for it to be the on 27th. More to follow.

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update — Nov 20

Current open PRs for review: 4 in 4.5 Milestone (-42)
Current open issues milestoned RC: 49 (-12)
Current open issues milestoned 5.0.0: 13 (-1)
Current open issues milestoned 5.0.1: 10 (+3)
Current open issues milestoned 5.0.x (fast follow): 74 (+6)
Current beta: Beta 5, released Thursday.
Current plugin: 4.4, released Thursday.
Next release: 5.0 RC, to be released later today.

As previously noted, we missed yesterday’s date by a small margin, as we had a few remaining items in 4.5. Now 4.5 is soon to be ready to release, and we’ll be able to proceed with 5.0 RC.

Note: this is a daily update on progress towards WordPress 5.0, as outlined in this post. This status update is also shared in the #core-editor channel in Slack.

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 19

Current open PRs for review: 46 in 4.5 Milestone (+1)
Current open issues milestoned RC: 61 (-1)
Current open issues milestoned 5.0.0: 14 (+1)
Current open issues milestoned 5.0.1: 7 (-1)
Current open issues milestoned 5.0.x (fast follow): 68 (+1)
Current beta: Beta 5, released Thursday.
Current plugin: 4.4, released Thursday.
Next release: 5.0 RC, to be released later today.

Note: this is a daily update on progress towards WordPress 5.0, as outlined in this post. This status update is also shared in the #core-editor channel in Slack.

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 16

Current open PRs for review: 45 in 4.5 Milestone (+5)
Current open issues milestoned RC: 62 (-45) — (This has been heavily triaged today).
Current open issues milestoned 5.0.0: 13 (+3)
Current open issues milestoned 5.0.1: 8 (+4)
Current open issues milestoned 5.0.x (fast follow): 67 (+30)
Current beta: Beta 5, released yesterday.
Current plugin: 4.4, released yesterday.
Next release: 5.0 RC, planned for Monday.

Note: this is a daily update on progress towards WordPress 5.0, as outlined in this post. This status update is also shared in the #core-editor channel in Slack.

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 13

Current open PRs for review: 44 in 4.4 Milestones (+9)
Current open issues milestoned RC: 148 (-14)
Current open issues milestoned 5.0.0: 3 (+1)
Current open issues milestoned 5.0.1: 2
Current open issues milestoned 5.0.x (fast follow): 19 (+4)
Current beta: Beta 4, released today.
Current plugin: 4.3, released yesterday.
Next beta: Beta 5, planned for Thursday.

Note: this is a daily update on progress towards WordPress 5.0, as outlined in this post. This status update is also shared in the #core-editor channel in Slack.

What’s new in Gutenberg? (12th November)

This update gathers a big number of fixes and improvements. It also completes many accessibility tasks — the original milestone for blockers is now closed.

Version 4.3 is fully released and Beta 4 will be coming later in the day.

Showing integration with the 2019 theme

4.3 / WordPress 5.0 (Beta 4) 🐺

Bug Fixes

Other Changes

Testing

Documentation

Mobile Apps

Deprecations removed with this version.

Status Update

  • Current PRs for review: 35 in 4.4 Milestone.
  • Open issues in 5.0 RC: 162.
  • Open issues in 5.0.0: 2.
  • Open issues in 5.0.1: 2.
  • Open issues in 5.0.x (fast follow): 15.
  • Current beta: Beta 3, November 5.
  • Current plugin: 4.3, released today.
  • Next beta: Beta 4, planned for today.

#core-editor, #editor, #gutenberg

What’s new in Gutenberg? (19th October)

This update is considered to be the feature complete for starting the WordPress 5.0 cycle.

Highlights include a block navigation system that can be used to access child and parent blocks within nested blocks easily. It also works as a way to navigate quickly through all the blocks in post. This is a top level affordance that works as a “path” finder and would be the basis for many of the phase 2 layout implementations.

Alternative mechanism for selecting nested groups.

There is also a new block, new style variations for Table, support for video backgrounds in the newly renamed Cover block, accessible date and color pickers, better visibility for style variations, and an “options” modal similar to the former “screen options” to toggle document and meta-boxes on and off.

And this one shows a convenient block for splitting media and text in two columns with mid resizing. In phase 2, this can be the base for internal resizing of columns:

The next step is going to be to freeze the numerous APIs while bugs and outstanding backwards-compatibility issues are addressed.

4.1 is at the release candidate stage, which can be grabbed here.

4.1 🎾

Bug Fixes

Other Changes

Mobile Native

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

What’s new in Gutenberg? (11th October)

4.0 is at the release candidate stage, which can be grabbed here.

Our 40th release is going to be a long one. Main changes are the introduction of a new data structure for RichText that will allow building sophisticated interfaces for inline content that we can make portable and relevant to mobile too.

It also has improvements for blocks, a way to set a different color as the overlay for Cover Image, a new font size picker that is clearer to use and scales much better, a cool Pullquote style variation, etc. This crosses a lot of the pending items.

There are also several interface improvements, including the ability to search categories, post locking when multiple people interact with the editor, better handling of floats, and many more.

Updated Font Size Picker component

4.0 🍯

Bug Fixes

Other Changes

Mobile

Deprecations removed with this version.

#core-editor, #editor, #gutenberg

Dev Chat Summary: October 10 (5.0 Week 2)

This post summarizes the dev chat meeting from October 10th (agenda, Slack archive).

5.0 planning

  • See @pento’s WordPress 5.0 for Contributors and Committers post:
    • “If you’re an experienced contributor or committer who has time available during the WordPress 5.0 release cycle, and want to be able to make meaningful contributions towards making WordPress 5.0 awesome” … “Please reply to this post with information about your availability, what components of WordPress you have experience in, and (if you haven’t got involved with Gutenberg yet) what you feel has been getting in the way.”
    • In that post are some direct actions you can take to help contribute to 5.0, otherwise please review and comment if you’ll be around during the 5.0 release cycle… thanks!
  • Also see review @pento‘s 5.0 commit/branch details if you plan to contribute during the 5.0 release cycle
  • @pento: if you have time to help, please review tickets in the 5.0 milestone to determine whether to keep it in 5.0 (Gutenberg-related), or move to 5.0.1 (other bug fix) or 5.1 (other feature)
  • @kadamwhiterequest for help testing Lazily Evaluate Translation Strings (#41305) with input requested by the end of this working week to help remove the blocker to further Gutenberg localization work
  • Plans for an updated readme.html to be committed with contributions open until RC
  • @chanthaboune: collecting blocker items and dates across team reps, will post listing to Make/Core, if you have items to add to the listing please ping @chanthaboune directly
    • @matt: 5.0 baseline and goal is 4.9.8 + Gutenberg, thus a lot of things that may have been considered blockers in past major releases are probably going to be reclassified as “nice to have”
  • @matveb: last JS package included in the Gutenberg 4.0 RC, on track and could be ready for end of the week

Updates from focus leads and component maintainers

General announcements

  • See @matt‘s post for details on the Gutenberg Phase 2 Leads, @alexislloyd (design and product) and @youknowriad (technical)
    • Phase 2 is about thinking outside the box, namely the post and page box, to allow Gutenberg to handle entire-site layouts. We will replace widgets with blocks, so any block will be able to be used in any registered “sidebar” for legacy themes, and we will upgrade “menus” to a navigation block.
    • Phases 3 and 4 of Gutenberg at WordCamp US in December.
  • @audrasjb: a11y team reorganizing, will discuss during next week’s meeting
  • @chanthaboune: as teams identify new/updated team reps, please follow notes on team rep orientation

Next meeting

The next meeting will take place on October 17, 2018 at 20: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.

#5-0, #a11y, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps

Dev Chat Summary: September 26th (4.9.9 week 7)

This post summarizes the dev chat meeting from September 26th (agenda, Slack archive).

4.9.9 and 5.0 updates

  • @schlessera: just about time to begin work on the 5.0 release cycle
    • @antpb and I will step back as release leads and wind down the 4.9.9 release
    • Over the next couple of weeks we will start coordinating the transition to ease into 5.0 release cycle
    • Will review the work that teams are already in the middle of and determine how best to proceed
    • Announcing this change as soon as possible to provide a longer transition period to smoothly transport as much work over as possible
  • @chanthaboune: “I lead the open source teams at Automattic and am a full time sponsored volunteer to the WordPress Project.”
    • We will reach out to team reps, discuss what you’ve been working on, and what we can do to keep things moving forward so that we can make sure everyone is heard as we settle in for 5.0
    • Current understanding is that @matt is leading 5.0 and any other leads are yet to be determined
  • @jorbin: concern with canceling 4.9.9 due to upcoming PHP7.3 release, some things need to be done to make sure WordPress runs fine on this new version of PHP, I want to ensure the version of WordPress in use on December 13th is compatible with PHP7.3, a very small scoped 4.9.9 may still be needed from myself and ideally @sergeybiryukov @pento @schlessera as well
  • @desrosj: #44416 and #44771 appear to be the open PHP 7.3 compatibility tickets in Trac
  • @pento: seems possible to wrangle a small 4.9.9 release with PHP 7.3 related bug fixes, while 5.0 is ramping up
  • @matveb: Gutenberg leads are near ready to start planning merge proposal for Gutenberg, currently focused on finishing the core Gutenberg tasks, @youknowriad has made a proposal for how JS packages could work
  • @youknowriad: recommend iterative merge vs. a big merge proposal, technical proposal on how this would work was shared in #core-js meetings
  • @sergeybiryukov: some new hooks or enhancements already backported to the 4.9 branch, will need to determine whether or not that should be reverted
  • @jeffpaul: in summary… (1) it appears like a possible agreement with @jorbin @pento (and possibly others who’ve been “voluntold” but yet to confirm) to work on a 4.9.9 focused solely on PHP 7.3 support and (2) @chanthaboune will review existing 4.9.9 work with team reps to see how that should be handled with the 5.0 cycle likely starting shortly

Updates from focus leads and component maintainers

  • The Editor / Gutenberg team released v3.9 last week including the ability to create reusable templates of blocks and exporting them to a JSON file
  • The JavaScript team posted this week’s meeting summary and specifically called for help looking for npm maintainers, so please let them know if you’re interested and available. Related to that, @youknowriad shared #44987 and is looking for review there.

General announcements

  • @psykro continues to look for review and feedback on the alternate devchat proposal
  • @joyously: Theme Review Team discussing what to allow theme authors to put in the admin, possibly allowing themes the same interface as plugins do with a readme.txt file and a View Details link to enhance the theme documentation, change logs, screenshots, upsells. Will look to have discussion in Core Trac ticket or Make/Themes post (and cross-post to Make/Core).

Next meeting

The next meeting will take place on October 3, 2018 at 20: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.

#4-9-9, #5-0, #core, #core-editor, #core-js, #dev-chat, #gutenberg, #summary