14:30 #startmeeting Weekly Main Inclusion Requests status 14:30 Meeting started at 14:30:30 UTC. The chair is slyon. Information about MeetBot at https://wiki.ubuntu.com/meetingology 14:30 Available commands: action, commands, idea, info, link, nick 14:30 Ping for MIR meeting - didrocks joalif slyon sarnold c_paelzer jamespage ( eslerm dviererbe ) 14:30 good morning 14:30 hello o/ 14:31 some people are on a canonical event, so we can expect reduced attendance 14:31 this is already more than I expected :) 14:31 I did a brief pre-check for today's meeting: It should be a quick one ;-) 14:31 #topic current component mismatches 14:31 Mission: Identify required actions and spread the load among the teams 14:31 #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 14:31 #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg 14:32 ^ the reports seem broken (empty) 14:32 But they showed nothing unusual earlier today. All known in c-m and c-m-p 14:32 #topic New MIRs 14:32 Mission: ensure to assign all incoming reviews for fast processing 14:32 #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir 14:32 I never use the .txt versions so I can't quite say what normal looks like https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.txt 14:33 right, the HTML report also shows lots of stuff. Looks like we're in the middle of archive opening ;-) https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.html 14:34 this one looks way more like what I expected https://people.canonical.com/~ubuntu-archive/component-mismatches.txt 14:35 yeah, there's enough here that I think we're seeing "archive being opened" broken, not "something's busted with the cronjob" broken 14:35 right, we should probably skip ahead until after pre-release freeze 14:35 We don't have any new MIRs in our queue. 14:35 #topic Incomplete bugs / questions 14:35 Mission: Identify required actions and spread the load among the teams 14:35 #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir 14:36 No updates since last week's meeting 14:36 #topic Process/Documentation improvements 14:36 Mission: Review pending process/documentation pull-requests or issues 14:36 #link https://github.com/canonical/ubuntu-mir/pulls 14:36 #link https://github.com/canonical/ubuntu-mir/issues 14:36 No open Issues or PRs 14:36 #topic MIR related Security Review Queue 14:36 Mission: Check on progress, do deadlines seem doable? 14:36 #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir 14:36 Internal link 14:36 #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 14:37 I've just finished reviewing dbus-broker earlier today (LP: #2015538), which we should put into the security queue (cc seb128) 14:38 how are the queues processing sarnold/eslerm? Any update since last week? 14:38 I believe eslerm has been working on the printing libs, he's been discussing coverity bugs with upstream author; I wouldn't expect much progress for the next two weeks 14:38 s/bugs/findings/ 14:38 ACK. 14:39 #topic Any other business? 14:39 I wouldn't be surprised if next week's meeting doesn't happen; the week after that, I'm on PTO; so, possibly, it'll be a few weeks for me 14:40 Right. We did have in-person MIR meetings in the past at engineering sprints. But that's not guaranteed. 14:40 I guess many of us will meet at the sprint next week! 14:40 I nothing else, that's all for this week! 14:41 woot, thanks slyon, eslerm :) 14:41 \o/ 14:41 #endmeeting