Dev Chat Agenda: December 12th

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 is the agenda for the weekly devchat meeting on Wednesday, 12th December 2018, 21:00 GMT:

Holiday times for dev chats: should we skip next 2-3?
5.0.1 planning and updates
Updates from focus leads and component maintainers
General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress 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/..

#5-0, #agenda, #core, #dev-chat

Gary Pendergast 8:35 pm on December 12, 2018

I’d also like to have a quick chat about the 5.1 schedule and scope. 🙂
justlevine 8:39 pm on December 12, 2018

Would love to see discussion regarding the release guidelines in light of the 5.0 cycle!
Things like whether there is an expected enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. freeze on 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 (as it says in the handbook), if there should be minimum time between the enhancement freeze -> release (and how .x releases differ from major releases), etc.

Also, since the next set of 5.0.x releases have seemingly been earmarked for 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/ enhancements (vs the general handling of .x releases), are there any considerations we should be making?
- Gary Pendergast 9:01 pm on December 12, 2018
  
  Thanks for the comment, @justlevine!
  
  This topic is probably best suited for a post on this blogblog (versus network, site), as there’s a lot to go over. The next few 5.0.x releases will certainly have a lot of blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor fixes, but things outside of that can also be considered. 🙂

Comments are closed.

Welcome!

Communication

Share this: