DeveloperServices/TeamMeetings/2015-06-30: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 36: Line 36:


== Other business ==
== Other business ==
* [lmandel] Adding bug links for stand-up items
** Dev work is largely tracked in bugs already. fubar, bkero and I discussed tracking more ops work in bugs as well. Can we start to link to bugs in our stand-up reports so that it's easier to follow-up on work?
* [lmandel] Q3 planning
** It's that time. We'll discuss on Thu and should have our deliverables set by end of next week.


== PTOs, etc ==
== PTOs, etc ==

Revision as of 17:53, 30 June 2015

« previous meetingindexnext week » create?

Meeting Info

  • 11 am Pacific Time
  • Vidyo room: DeveloperServices
  • Backchannel in #vcs

Hot items

  • On Call Handoff!!!

Stand-up

Last week

What did you accomplish in Whistler? What is notable?

  • bkero
  • fubar
  • gps
  • hwine
  • lmandel
    • Whistler
      • Discussions about release process, release and pre-release data from FHR/Telemetry, developer builds, build system, representation of platform ops
  • smacleod

Planned for this week

  • bkero
  • fubar
  • gps
  • hwine
  • lmandel
    • Follow-up from Whistler, ship 39
  • smacleod

Other business

  • [lmandel] Adding bug links for stand-up items
    • Dev work is largely tracked in bugs already. fubar, bkero and I discussed tracking more ops work in bugs as well. Can we start to link to bugs in our stand-up reports so that it's easier to follow-up on work?
  • [lmandel] Q3 planning
    • It's that time. We'll discuss on Thu and should have our deliverables set by end of next week.

PTOs, etc

  • Wed is Canada Day (Lawrence, Steven)
  • Fri is Independence Day (Ben, Greg, Hal, Kendall)

Links

Q2 Goals