ReleaseEngineering/2010 All-Hands Planning

From MozillaWiki
Jump to: navigation, search



(Keynotes are scheduled at the MV Center for Performing Arts)

9:30 Keynotes
13:00-14:00 Lunch
14:00 RelEng group mtg
15:00-15:30 Break
15:30 killing tinderbox for good? (JK conf room, 2nd floor) coop, dbaron (probably can't make it on Monday), dustin (if still going at 23:30)


Tuesday moz-wide meetings

9:30 communication deaves
12:00-13:00 Lunch
13:30 integrating mobile infra better bhearsum
15:00-15:30 Break
15:30 Release Day process. How to speed things up? How can RelEng help? catlee,bhearsum,LegNeato,armenzg
18:00 Dine-about


Wednesday moz-wide meetings

10:30 SUT meetup (Android Talos/Unit tests) aki bear coop jmaher ctalbert bmoss + anyone interested
13:00 mozharness aki
14:00 War on Orange (WoO) ctalbert, coop
15:00-15:30 Break
15:30 mozillapulse bear/catlee


Thursday moz-wide meetings

10:00 IT/releng
IT: phong/jabba/jlazaro/zandr
11:00 Releng New Hire Brownbag armen
12:00-13:00 lunch
14:00 google 6-week release schedule 10-f
15:00-15:30 Break
16:00 hyperbranching 10f
evening party in Los Gatos

Proposed Sessions

  • Mozharness (aki?)
  • Build messaging with pulse (bear/catlee?)
  • How do we kill tinderbox for good? (coop?)
  • [Thursday@11am] RelEng Brownbag (armenzg)
  • bug 614629 - focusing external interfaces at
  • L10n awesomeness
    • Unifying all-locales, shipped-locales and l10n-changesets
    • Doing a stub installer that pulls in required langpacks at install time, and stop doing full repacks as part of nightly / release build automation.

Group internal stuff

  • Development environments (aka, staging-master sucks)
    • please let's do this one in the first two days of the week so I can participate (lsblakk)
    • Better ways to stage buildbot changes using some "build this master from scratch" scripts --Djmitche 12:41, 3 December 2010 (PST)
  • Best Practices
    • Agreeing on a "normal" way of solving particular kinds of problems, such that doing it the non-normal way requires a good bit of convincing (e.g., got some data -> use static files in hg; got a web service -> host it on ___; got some useful command-line scripts -> put them in build/tools).
      • building new stuff this way
      • moving old stuff to this system
      • documenting what we have
    • finishing projects so we don't have a "new way" and an "older way" and a "slightly older way" and "oh, we might still do it that way, too"
  • Intergrating Mobile infra better (bhearsum)
  • New Puppet Infra --Djmitche 08:51, 8 December 2010 (PST)
  • Last bits of colo isolation, how to do the following without leaving a colo, and how to keep things in sync (bhearsum):
    • Upload/download builds
    • buildbot DB
    • graph server
    • hg