Dev Chat Summary: September 4

@audrasjb was our chat leader today and did an excellent job as usual. (backscroll)

Announcements

JB shared some posts that are currently open for discussion, feedback, or volunteering.

  • About page design: https://make.wordpress.org/design/2019/08/28/discussion-about-the-about-page/
  • New feature plugin proposal: https://make.wordpress.org/core/2019/09/04/feature-plugin-proposal-privacy-data-request-form/

Upcoming Release(s) Update

  • WordPress 5.2.3
    • This is due out today!
    • Right after devchat the plan is to begin the final packaging and release process.
  • WordPress 5.3 has a new batch of focus leads!
    • @miker joined the team as Marketing Focus Lead
    • @ianbelanger joined the team as Default Theme Wrangler
    • @andersnoren joined the team as Default Theme Designer
  • WordPress 5.3 also has an updated timeline posted here: https://make.wordpress.org/core/5-3/
  • All bug scrubs are listed here: https://make.wordpress.org/core/2019/08/27/bug-scrub-schedule-for-5-3/ . The next general bug scrub is Sept 5, 2019 at 14:00 UTC in #core channel.

Call for Component Maintainers

  • @azaozz has put up a challenge to his fellow maintainers for 5.3 (and hopefully beyond!) https://make.wordpress.org/core/2019/08/30/component-maintainers-in-5-3/
  • @chanthaboune shared that the maintainers of the default themes are due for a change
    • @ianbelanger and @williampatton raised their hands to help with that transition.
    • @clorith suggested it’s time to have a clearer support plan for working with default themes

Open Floor

  • If anyone is local to the Orlando area, there’s a community event coming up. https://www.meetup.com/WordPress-Orlando/events/263847409/

Important WP5.3 Dates

  • September 23: 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 (begin writing 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 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. and About page, and last chance to merge feature projects)
  • September 30: Beta 2 (continue writing Dev Notes and About page)
  • October 7: Beta 3 (continue writing Dev Notes and About page, and soft string freeze)
  • October 15: Release candidaterelease 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 (publish Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. with Dev Notes, commit About page, begin drafting release post, and hard string freeze)
  • October 22: Release candidate 2 (update About page images, and continue drafting release post) (also @audrasjb‘s birthday!)
  • October 29: Release candidate 3 (update About page images, and continue drafting release post)
  • November 5: Release candidate 4 (if needed)
  • November 11: Dry run for release of WordPress 5.3 and 24 hour code freeze.
  • November 12: Release Day!

#devchat #summary #5-2-3 #5-3

#dev-chat