@whyisjake led the chat on this agenda.
Highlighted/Need Feedback Blog (versus network, site) Posts
@whyisjake shared a few blog posts and announcements:
WordPress 5.4.2 was planned to be released Wednesday 10th after the devchat (and successfully shipped with the help of our amazing contributors). This version includes six security fixes and many 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. fixes. More details about what is inside can be found on the version page.
@pbiron reminded that three feature plugins will be included in WordPress 5.5. Lazy loading of images, themes, and plugins, auto-updates, and XML sitemaps.
Some tickets for enhancements/features will need some help, testing, or feedbacks before 5.5 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. 1 (targeted date: July 7th, 2020): #40351, #41750, #33161, #47456, #43738.
@audrasjb mentioned some other tickets on which the 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) team needs help and feedback. #49459 and #49651 need Editor team feedback and #30155, #47120 and #48170 will need feedback and expertise from the Media team.
@paaljoachim said he’s working on #16020 and would need some feedback on it.
@enricosorcinelli mentioned that #21676 got some new attentions, and could be a possible candidate to ship in 5.5.
@justinahinon said that he reached out to people interested in helping on hosting APAC devchats proposed here. There is a plan to discuss in the #core channel about the outcomes of the meetings and a possible schedule (a note about that will be published soon on Make/Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog).
Related to that, @yvettesonneveld shared what they have been doing for marketing coffee breaks and that was very helpful in recruiting and retaining contributors. Updates for this can be found here.
@jeffpaul proposed some additions to the Releasing Major Version and Glossary handbooks. These additions are about the
early ticket Created for both bug reports and feature development on the bug tracker. definition and how they are handled during the release process. This is a result of discussions at WCEU Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. and received helpful feedback from @davidb, @desrosj, and @joemcgill. Some contributors had a discussion about that, and you can rollback to here to follow.
@enricosorcinelli reminded that they are some tickets that have been milestoned for each release since 5.0 but hadn’t received any attention in their life cycle. These are #43516, #43517.
This closed the devchat discussions to leave room for WordPress 5.4.2 release party.
#5-4-2, #5-5, #summary