Dev chat summary, July 8, 2020

@whyisjake hosted from this agenda, edited by @marybaum.


WordPress 5.5 beta 1 landed yesterday! Tell everyone you know to download it, test everything and try to break all the new features—that’s what 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. releases are for.

@audrasjb  shared some stats: as of Beta 1, WordPress 5.5 has 190 new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac.! A lively discussion followed, covering stats and going back several years, in some detail. Check it out here.

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. 8.5 is live!

This is the last Gutenberg release going into WordPress 5.5 and is the major focus for this month.

From now until the final release of WordPress 5.5, Gutenberg is also in a feature freeze. That means the only tickets that will move on are 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 and code regressions; everything else will get punted to 5.6 or a future release.

Another result of the feature freeze is that TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and the Gutenberg should both see fewer last-minute commits. So look for the Beta 2 release party to start a little earlier next week (July 14) in a bow to our European contributors’ schedules.

@pbiron  #50449 could use some 
from those who are knowledgeable about RTL
#50449: Sitemap style for RTL sites

Component check-in

@marybaum announced a schedule change for the about page. She’ll attach the copy and layout to the ticketticket Created for both bug reports and feature development on the bug tracker. for 5.5 on Friday. She issued shoutouts to new contributors @abhanonstopnewsuk and @yvettesonneveld for their research with folks in the Marketing team, and @estelaris for in-depth research in design.

@justinahinon updated the group on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 5.5 and issued a call for writers. You can see progress on the Trac notes on this Google Sheet  and Gutenberg-related notes here on GitHub.   

Open Floor

@desrosj has a post coming soon that will focus the ongoing discussion of exactly which bugs and tasks get the ticket love in two periods: the beta-to-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). period (for 5.5, that’s now: it started July 7 and will run until RC1 lands on July 28) and the RC-to-release period (for 5.5, the two weeks from July28 to August 11).  

For now, you can see earlier discussion on the topic here.

Finally, @whyisjake brought up a pull request that got his attention because of licensing issues it raises for part of the contributor toolchain.

#5-5-2, #devchat, #summary

#5-5, #dev-chat