As our Release Coordinator @francina was not available yesterday, @mapk led this chat. Thanks to all the attendees.
Announcements and highlighted posts
First announcement was Beta 1 of WordPress 5.3 that went out earlier this week. Every one is invited to help test it and report bugs and unexpected behaviors. The Beta 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. includes the first iteration of Twenty Twenty, the new default theme which development is ongoing on GitHub.
Here are some highlighted posts shared by @mapk:
@antpb also shared the Media component weekly report.
Upcoming Release Discussions
@mapk said Gutenberg 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/ team started a project board in the editor Github GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for the issues and pull requests that they’re hoping to get in or at least backport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. into 5.3.
Twenty Twenty lead @ianbelanger said the team is particularly looking for help on this issue.
@audrasjb made a post-Beta1 Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) update focus. 6 important tickets for the focus where committed just before the release. They are still 33 open tickets in the milestone. Everyone is invited to help tackle them and join the focus weekly bug 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 every Friday at 2 PM GMT+3.
@davidbaumwald remembered that there are dedicated bug scrubs for 5.3 with the schedule here which Beta 2 is scheduled for next Monday.
@desrosj noted that 5.3 Release 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). 1 is scheduled for October 15, and that the list of remaining tickets in the milestone needs to be empty by this date.
Calls from component maintainers
@audrasjb pointed out the 15 ready to be committed tickets in 5.3 milestone and asked for available committers attention on them.
Open Floor was quiet yesterday. And the chat ended up under one hour at 9:40 PM.