This post summarizes the dev chat meeting from October 3rd (agenda, Slack archive).
5.0 planning
- See @matt‘s post on plan for 5.0 and leads across the critical focuses involved in the release
- See also @youknowriad‘s post on the technical overview of Gutenberg integration for specifics on how 5.0 could progress
- See also @pento‘s post on the proposed release schedule
- Current release date is November 19th, could be pushed as late as November 27th if needed. If more time is needed, then we’ll move the release to January 22, 2019.
-
@pento: intention is to have 5.0 out (including some small fixes to ensure compatibility) before PHP 7.3 is released. If 5.0 delays significantly, then there will be a 4.9.9 release with just the PHP 7.3 compatibility fixes.
-
@joen: fast approaching UI freeze, likely by RC if not by Beta 1 (October 19th), though bugs and testing feedback might force us to have to make changes
-
@matveb: feature freeze during betas, towards end of the month, based on work remaining in Make/Core update
- Twenty Nineteen theme will be included in 5.0 with discussions in #core-themes, though the 5.0 release won’t be delayed if the theme evolves slowly, development will take place on GitHub with @kjellr publishing a post on the topic shortly
-
@laurelfulford creating Trac tickets for bundled theme updates
-
@chanthaboune still following up with component teams to discuss concerns on shift from 4.9.9 to 5.0
-
@pento still working to determine the 5.0 release branch in SVN, likely not viable to work from
trunk for 5.0, may branch 5.0 from 4.9 and work there, a Make/Core post will come once that’s determined
-
@matt: open to having 5.0.x releases that are like the 4.9.x releases that bring in some larger updates or improvements we push off (e.g., servehappy the WordPress PHP education initiative)
-
@youknowriad: will continue updating Gutenberg documentation in the plugin (they’re markdown files) while making it clear in the Handbook which version you’re looking at:
- Is it the integrated version into Core (the default)
- Is it the handbook for the updates coming to Core (the current version in the plugin)
- A version selector could also be integrated
-
@lonelyvegan: list of
documentation issues noted in GitHub repo
-
@matveb: note plan to reorganize handbook to give more visibility to vision/guidelines
-
@danielbachhuber: collecting REST API-related issues for 5.0, any help on them would be greatly appreciated
-
@jorbin: 400+ open tickets in the 5.0 milestone needing a bug scrub
- Help appreciated on tickets labeled as
Needs Testing or Needs Technical Feedback
-
@desrosj: can help write dev notes needed
-
@joemcgill: ideally Gutenberg goes through feature merge process to ensure security/a11y/etc. reviews
Updates from focus leads and component maintainers
General announcements
Next meeting
The next meeting will take place on October 10, 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, #core, #dev-chat, #summary
