Roundtable!

• morgamic
  • marketing discussion
  • socorro work week
• 
  • Pinching webdevs not wearing green
  • Socorro Postgres work week
  • CTAW phone call with SocialActions
  • A bit 'o the Prior Art
• wenzel
  • mozilla.com contextual landing pages: painfully dirty IE hacks
  • starting to work on AMO 5.0.4
• laura
  • vacation :)
  • SUMO 1.0 freeze tonight on track, 1.1 next Tues on track
  • bunch o' prior art stuff to check in
  • Wearing Guinness tshirt and my horse has a shamrock on his butt (visible here)
• jbalogh
  • refactored the bot to track failing tests by name
  • up to 75% code coverage in testing, from 0% (∞ times better)
  • AMO bugs for 5.0.4
  • PTO Friday, incoming sister
• Lars
  • Socorro Work Week
    • fine tooth combing monitor/processor
    • learned to interpret PostgreSQL explain
    • tons of other stuff
  • Train rides
  • Implementing changes to monitor/processor
• lorchard
  • bandwagon & AMO patches
  • puttering along with BYOB
• clouserw
  • planning 5.0.4
  • doing reviews and patches for AMO
  • getting ready to leave on wednesday
  • need a product-details person while I'm gone
  • gave austin laser eyes in his photo up there ^^
• neilio
  • SFX bug whippage
  • Bandwagon wireframes
  • AMO category page redesign work
  • SUMO UX audit bits, commenting on UX-related bugs, etc.
  • Labs 2.0 redesign
  • Chatted with Blizzard on reporter.mozilla.org redesign
  • I am wearing this shirt today.

Yummy Tidbits

• 1nt3rn pr0j3ctz
• on-site travel!
  • Wednesday - dinner
  • Thursday afternoon - some bonding
  • Friday - open as travel day
• brief summary of pg experts visit
  • Fouine rocks
• IT SLA draft
  • Stage updates broke last week 3 times, 4-8 hours would be crippling (bug filed to monitor this)
  • AMO last thursday - pushed updates then took off, and didn't respond to bugs until we made it blocker - would like people to stick around for 10-20 minutes until we verify the push
  • SUMO replication was down for 2 weeks (which was really the entire stage cluster db), they got paged and nobody fixed it (is there a bug filed to monitor this?) -- also took 24 hours to even get caught up