Revision as of 18:03, 27 January 2009

Open Items

IT follow-up
- Dedicated tools/SUMO server online
- Read-only slave for AMO (and others in future) DB
- Had a chat about turnaround times for access, troubleshooting tickets -- what do you think is acceptable turnaround time?
  - Access bugs: 8 hours -- grant access by end of 8 hours window (critical)
  - Production problems: 30 min -- some kind of response or update to team (blocker)
  - Stage updates: 4-8 hours -- have stage updated so we can unblock QA and testing (major/critical depending on whether or not it blocks QA)
  - Other: 24 hours -- have an update with ETA in other bugs within 1day (normal)
- Tips
  - If you're going to need commit access, hardware, etc. in the future, file the bug before you get stuck on those things
  - Think about things you'll need from IT -- if we file the bug sooner it'll get done sooner
Evals -- thank you for having evals in, we had ours in on time! Peer evals going out this week.

Intros for Jeff -- as we do the roundtable, introduce yourself
morgamic
- Mt View trip, which translates to lots of meetings
- Spent time with Wil, Jeff, AMO team
- kick-off meetings for marketing, labs projects

@@ Line 11: / Line 11: @@
 *** If you're going to need commit access, hardware, etc. in the future, file the bug before you get stuck on those things
 *** Think about things you'll need from IT -- if we file the bug sooner it'll get done sooner
-** Evals -- thank you for having evals in, we had ours in on time!  Peer evals going out this week.
+* Evals -- thank you for having evals in, we had ours in on time!  Peer evals going out this week.
 = Roundtable =