Release Management/Goals/2014Q4

Release Management Q4 2014 Goals

<platform> denotes goals that are listed on the platform Q4 goals list

Release Management General

Release Quality - Improve automation / reduce risk of manual errors

• [Lukas] Create automated release checklist (maybe based on ship-it)
• [Lukas] Fully automate Product-Details (if missed in Q3)
  • see https://github.com/mozilla/relman-tools/tree/master/auto-pd which is a bit janky because of ftp data pulled (version is not always correct, needs more robust tests before it can be automated)

• [Sylvestre] Automate manual portions of ship-it
  • pull in recent changesets from tbpl/treeherder (bug 1040759)
  • create new l10n milestone and pull in l10n changesets from dashboard (bug 1035458)
  • auto populate partials (bug 1049689)

• [Sylvestre] Automate the publication of Firefox Android
  • Use the Google play API to push APK automatically (bug 1045531)

Release Quality - Find issues earlier

• [Lukas] Continued work on the Release Readiness Dashboard to reflect accurately the current release schemas
  • Add in ESR
  • Get Firefox Android queries/groups created
  • Triage queries
• [Lawrence] Add new repository hooks
  • Create checkIID hook to catch required IIDL bumps

Enterprise - Improve Quality for Orgs using ESR

• [Benjamin] Investigate Automation of building MSI Installers
• [Benjamin] Move ESR Strategy Forward

Communication

Expand contributor involvement

• [?] Define contributor pathways
  • Triage of Desktop, Mobile, B2G, Platform, Services (?) bugs

• [Haseeb]
  • Start shadowing Benjamin on Nightly Triage
  • Start attending CrashStats Meeting
  • Start reading Agile/Release Management Book

Firefox Desktop/Mobile

• [Lukas] <platform> Throttling improvements - continue to collect data for FF31, then implement updated SOP
  • Round 2 of experiments to get within the same week as release
  • This will get a faster uptake on new features in product release - great for press/marketing efforts to get more Mozillians
• [Lukas] <platform> All-Hands potential sessions:
  • Can we get commitments to turning off any intermittent orange tests and then build back up?
  • Getting to Daily Betas - what's left?
  • L10n, the black box and what can we open up to greater understanding?
  • Learning from our mass-chemspill - Port-Mortem and actions to take forward
  • Release Notes & PR - overhaul and creating a high-signal method for generation of our release communications
  • Where are we in the release cycle and what does that mean to you? (dev/qa/pr/other?)

Firefox OS

• [all] Participate in B2G test days

Special Projects

• [Lukas] Ascend Project
  • Running the program
  • Prepare metrics (visuals) to help summarize and be able to talk about how Ascend #1 went and what's next

• [Haseeb] Hillhacks
  • Successfully run the hillhacks event

• [Sylvestre] Testing
  • Get test suite to green by separating oranges and creating a strategy to determine if a reported orange failure is a real failure
  • Incorporate C++ coverage report in builds bug 890116
  • Incorporate static analyzer in builds and report on diffs
  • Better tests
  • Coding style
  • Improve documentation/usability of the various tests
  • Implement some features in treeherder (like the ETA) bug 1052397

Personal Development

• [Bhavana]
• [Lawrence] Learn about Google Analytics
• [Lukas] Back to guitar playing! Get above 80% on at least 2 songs I used to play, and get 2 new songs into the above 80% range
• [Sylvestre] Continue Spanish lessons
• [Benjamin] Take some Banjo classes
• [Haseeb] Focus on communications skill