Dev Chat Agenda for December 4, 2019

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Here is the agenda for the weekly meeting happening later today: Wednesday, December 4, 2019, at 09:00 PM UTC.

Announcements

Upcoming Releases

5.3.1 – WP 5.3.1 week 3: bug scrubs schedule
5.4 – WordPress 5.4 – Open Call for Tickets

Highlighted Blogblog (versus network, site) Posts

Blog Posts Needing Review/Feedback/Help

WP Notify hiatus till January 2020

Components Check-in

News from components
Components up for adoption (Comments, Filesystem API and Rewrite Rules)
Components that need more hands on deck

Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #core, #dev-chat

Francesca Marano 10:25 am on December 4, 2019

I’ll start 🙂

In the retrospective post I proposed to form a working group to evaluate the possibility to change the release model used.
I would like to schedule a dedicated dev chat where all parties interested could come together to kick this off.
Disclaimer: I won’t be available to work on this, but it seems to be a very hot topic and I would like to see it explored properly. I can help facilitate the first steps if needed. If not, even better!
- Jb Audras 11:50 am on December 4, 2019
  
  Happy to help with my little experience! 💜
Jb Audras 11:49 am on December 4, 2019

Hi @francina,
We need to set up a team and a schedule for 5.3.1.
- Francesca Marano 12:27 pm on December 4, 2019
  
  These fine folks raised their hands during November 20 chat
  @sergeybiryukov, @audrasjb, @amykamala, @marybaum, and @whyisjake
  For some reason, I remember also @justinahinon being available and voluntelling Sergey to be the lead 😉
  
  Let’s finalize this tonight.
  
  In terms of schedule, it’s my understanding that a minor doesn’t necessarily need 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. and 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).. Here is a template for a schedule https://make.wordpress.org/core/handbook/about/release-cycle/releasing-minor-versions/#schedule
  Does it seem doable?
  - Jake Spurlock 12:48 pm on December 4, 2019
    
    I’m available for the proposed release, but unavailable for the chat today. Schedule is feeling a little tight right now, but we can prolly make it work. Would love it pushed a week, but that gets us pretty close to the holidays.
  - Jb Audras 12:57 pm on December 4, 2019
    Here is my proposal:
    
    Thursday 5 20:00 UTC or so: 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.
    
    Tuesday 10: 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).
    
    Wednesday 11 or Thursday12 : final
    
    @whyisjake @francina
    - Jake Spurlock 12:59 pm on December 4, 2019
      
      Thursday + Thursday would be great.
      - Jb Audras 2:00 pm on December 4, 2019
        
        +1
imath 12:31 pm on December 4, 2019

Hi @francina thanks a lot for this agenda, I’ll try to attend this meeting as I’m interested about adopting for the « Comments » component. I had opportunities to contribute to a couple of tickets so far and I believe it’s a really nice feature I could bring some love to 😉
- andraganescu 9:37 am on December 9, 2019
  
  Hi @imath this is great news, the comments component really needs some serious attending. Francesca launched a call for people interested in taking on the challenge of the Comments component here:
  
  https://make.wordpress.org/core/2019/12/04/wordpress-5-4-open-call-for-tickets/#comment-37586
  - Mathieu Viet 10:09 am on December 9, 2019
    
    Thanks for the link 👍 I actually add a chat with Francesca & David about it ✅

Comments are closed.