Diff for "MeetingAgenda"

Not logged in - Log In / Register

Differences between revisions 104 and 105
Revision 104 as of 2009-10-08 20:52:43
Size: 6536
Editor: matsubara
Comment:
Revision 105 as of 2009-10-15 17:16:02
Size: 6364
Editor: matsubara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
  '''Thursday 15 Oct, 1500 UTC - 1545 UTC'''   '''Thursday 22 Oct, 1500 UTC - 1545 UTC'''
Line 97: Line 97:
* matsubara to trawl logs related to high load on edge on 2009-09-09 ~1830UTC and ping Chex about it
* matsubara to email the devel list about the new ErrorReportingUtility method
    * done
* matsubara to file a bug to have the HWSubmissionMissingFields oopses as informational only (note to self: see bug 438671 for more details)
    * filed https://bugs.edge.launchpad.net/malone/+bug/446660
* matsubara to look in lp-production-configs for the new oops prefixes.
* all QA contacts to inform their teams about the new QA column and what they should do about it.
* Chex to email the list about the new QA column in https://wiki.canonical.com/InformationInfrastructure/OSA/LPIncidentLog
* matsubara to file a bug on oops-tools to recognize new oops prefixes and sort out conflicting prefixes with losas
* Chex to check app server logs and apache logs to see if it can shed any light in the high load issue.
* adeuring to check with gmb about checkwatches failure
* danilos to check bug 438039, assess if it's really critical. if it's is, land a fix, if it's not, update the importance
* bigjools to investigate update-cache failure and reply back to the list
Line 131: Line 128:
 * 2009-10-15
  * DevelopmentMeeting20091015

Agenda of the next Launchpad Production Meeting

Launchpad Production Meetings are held on #launchpad-meeting on chat.freenode.net

The purpose of the meeting is to coordinate resolutions to Launchpad production issues. It's driven by the QA portion of the Releases Team.

The next Launchpad production meeting will be held at:

  • Thursday 22 Oct, 1500 UTC - 1545 UTC

You can add new items to the list of proposed items. If they don't make it onto this meeting's agenda, they'll most likely get onto the next meeting's agenda instead.

If you're going to discuss a private bug, please consider if it really needs to be private. If not, disclose it to the public for attendants benefit.

When there is no meeting

Occasionally, there is no Launchpad production meeting in a particular week. This may be due to conferences or holidays.

Proposed items

Propose items below along with your name. If you have pending SysAdmins requests (i.e. RT) that need attention, please add it here (or bring it up with your line manager who should know of a way to escalate it).

  • add here (and keep this line)

Apologies

Meeting Script

Intro

#startmeeting

Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.

Roll call

[TOPIC] Roll Call

Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!

Who should be here?

The old full team IRC meeting was abandoned on 11 Sept 2008. Only those below need to attend but everyone else is welcome.
  • Diogo (meeting co-chair)
  • Ursula (meeting co-chair)
  • DBA contact (stub)
  • LOSAs contact (Chex)
  • QA Contact from
    • Foundations (gary_poster)
    • Code (rockstar)
    • Soyuz (bigjools)
    • Translations (danilos)
    • Registry (sinzui)
    • Bugs (allenap)

Agenda

[TOPIC] Agenda

 * Actions from last meeting
 * Oops report & Critical Bugs & Broken scripts
 * Operations report (mthaddon/Chex/spm/mbarnett)
 * DBA report (stub)
 * Proposed items

Ugly but convenient for running meetings

[TOPIC] * Actions from last meeting
[TOPIC] * Oops report & Critical Bugs & Broken scripts
[TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
[TOPIC] * DBA report (stub)
[TOPIC] * Proposed items


  • (other items)

Actions from last meeting

* matsubara to file a bug on oops-tools to recognize new oops prefixes and sort out conflicting prefixes with losas
* Chex to check app server logs and apache logs to see if it can shed any light in the high load issue.
* adeuring to check with gmb about checkwatches failure
* danilos to check bug 438039, assess if it's really critical. if it's is, land a fix, if it's not, update the importance
* bigjools to investigate update-cache failure and reply back to the list

Closing

Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.

#endmeeting

Summaries of previous meetings

MeetingAgenda (last edited 2010-06-11 01:27:08 by ursinha)