Dev chat summary: August 21, 2019

Props to @francina, who led her first chat and will be the release coordinator for 5.3!

@marybaum is your chat reporter.


@chanthaboune kicked off the announcements with a comment that she’s working on a summary of the auto-update discussion from Tuesday afternoon.

Then she introduced @francina to the group, making the formal announcement that she’ll coordinate the 5.3 release.

Upcoming releases

5.2.3 to land on September 4

@francina took the floor to talk about planning for 5.2.3, asking @jeffpaul to report on his preliminary work, including two 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. scrubs, one of which he led and the other of which @marybaum led.

Several people noted that as of those two scrubs, the release now has all of its tickets committed and merged.

As the discussion progressed into scheduling and the naming of release leads, @davidbaumwald pointed out that anyone, anytime, can schedule and lead a bug scrub.

@karmatosed noted that the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Team hoped to see more scrubs throughout the project, with more people leading them.

After some discussion, with the group showing a clear preference for new faces on minor releases, @whyisjake emerged as the release leadRelease Lead The community member ultimately responsible for the Release. on 5.2.3.

His first official act was to confirm the preliminary schedule @jeffpaul had put together.

He also confirmed RC1 for Thursday, August 22, which did happen. (Go forth and test!)

You can find the rest of the schedule here.

Quote of the hour, from @whyisjake: “I don’t know if I’ve won the lottery or lost a bet.”

5.3 to land November 10

@francina referred the group to this post for 5.3 planning and scope.

Overall, the release will polish current interactions and make the UIs more user-friendly.

The release lead will be @matt; @francina will be the release coordinator. Other focus leads are in the post.

Three of the focus leads have yet to be named – but @chanthaboune will have those filled in the next week or so, well before the first 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. on September 23.

In the chat, @justinahinon volunteered to lead Docs. @desrosj and @marybaum said they’d be part of his squad.

Triage lead @davidbaumwald announced a preliminary schedule of bug scrubs:

#1 8/27/2019 18:00 UTC
#2 9/5/2019 14:00 UTC  (EU-Friendly)
#3 9/12/2019 05:00 UTC (APAC-Friendly)
#4 9/18/2019 13:00 UTC  (EU-Friendly)
#5 9/25/2019 23:00 UTC  (Late-Americas-Friendly)

Which led into a discussion of triage and bug scrubs in general: that anyone can lead one; that several teams are using them regularly; and that it might be helpful to consolidate and promote a list of scrubs across the Project.

Open floor

At the ten-minute mark, @francina suggested group members introduce themselves so she (and the team) could get to know everyone a little better.