Dev Chat Summary: January 2

Happy New Year everyone! Meeting archive is here.

5.0.3 Update

  • @audrasjb has been sorting tickets for the milestone 5.0.3.
  • There is some discussion over whether tickets should be backported if this is a true minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
  • Tomorrow there will be 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. scrub and times will be announced as a comment on these notes.
  • @audrasjb and @desrosj are leading 5.0.3 together.


  • @chanthaboune will track down the basics for this release and share what she finds.

Updates from focus leads and component maintainers


Looking into what can/should be deprecated as we move forward (the Playlist functionality was talked about as a potential). Meeting notes here.


A final documentation push is underway and lots of discussions around 5.0.3 planning.


  • @omarreiss let us know that developers can now run grunt build –dev again. More information here.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. meetings, Design, and 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. docs meetings start again next week, along with many other teams.

Open Floor

@desrosj proposed a new 2 step process for TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • Step 1: anyone that owns a ticketticket Created for both bug reports and feature development on the bug tracker. or is a component maintainer goes through their tickets and makes sure the correct labels are applied and that the tickets are still valid, and puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) to Future Release if it does not fit in with the current project priorities.
  • Step 2: any ticket in the 5.1 or 5.0.3 milestone that is tagged needs-patch or needs-refresh is punted to Future Release. Currently, this would match 101 tickets.

He will be writing up a post to expand futher.

#dev-chat #summary