Release Management/2014 Q1 Work Week/B2G Focus 2014 Notes

From MozillaWiki
Jump to: navigation, search

.* B2G 2014 Focus

  • Dogfooding
  • 1.3 (Preeti),1.4 (Preeti),1.5 (Bhavana) Releases - alternating between Preeti Bhavana
  • Have a basic Release Readiness Dashboard for B2G by Willie (shared with Desktop & Mobile)
  • The next Intern come-up and pick it up where Willie left off to improvise further or help with other tooling
  • Getting involved during the development phase maybe functional triage, Demo's
  • If we have an opportunity participate running features from PM point of view
  • Stability side
    • Getting symbols from partners is hard, figure out what's going worng there and have a better process
  • People are desensititive to deadlines or nagging, what are we doing wrong here ?
    • May be not adhereing to deadlines more strictly?
    • Accepting fixes even after the blocker date is done
    • could we do a developer interative mini get together to really see what they like and don't and see how we can work together
      • Right now we do have like issues like perf bugs, stability issues etc how do developes want to hear about that ?
    • The discussion(Eg: Schedule discussion) are happening on close lists, meetings which were not open to the public
    • Dev's get irritated about questions like "eta" etc, how do we overcome this ? Can we put that in any other way ?
  • Once 1.4 reaches RTP ensure the quality level for that hand-off
    • Ex : no outstanding RIL bugs
    • Regressions this cycle
    • Have a priority list of bugs which Release Mangement thinks are blockers
  • Clarifying roles for Taipei relman
    • Similar to relman
    • Ears to the ground on features being developed there - early feedback
    • Help with interviewing/onboarding
Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/2014_Q1_Work_Week/B2G_Focus_2014_Notes&oldid=910367"