Release Management/Goals/2013Q2

Drafted here: https://etherpad.mozilla.org/2013q2-goals

Higher Level Goals

• [DONE] [lsblakk] getting the relman dashboard up on paas, coordinating handoff to Kyle for sec review, dogfooding/bugfixes, evangelising to devs & managers as it's ready
  • we're looking into multi-user bugs, trying to pare down functionality to minimum viable for initial release
• [DONE] [akeybl] Take the next step in Rapid Betas - 2 betas per week when necessary, finding/driving parallelization opportunities for QA sign-off (for instance, bug verifications)
  • Full review being scheduled - see "Testing Necessary for QA Sign-off" email
• [DONE] [akeybl] Introduce Firefox for Android into new tier 1 stores, marketplaces, and catalogs
  • Yandex.Store integrated into release process
  • questions/concerns for stores standardized - business need, targeted locales/demographics, modification of APK, review process, update process, ability to remove from the store, etc.
  • Aruba, T-Store incoming still this quarter
• [ON TRACK] [akeybl] File all bugs necessary for releasing mobile as a Mozilla-updated release APK (eng, releng, webdev, support, etc.), create whitepaper explanation, and drive
• [DONE] [bajaj]Metro pre-release planning/launch (in support of engineering's "Uplift from mozilla-central to mozilla-aurora" goal)
  • Have had a couple of meetings with metro team where the idea was to uplift to Aurora during next merge
  • I have actions to check with l10n,get metrics for touch devices on all channels and guage if the uplift is worth the pain ?
  • Other metro team members(Asa) had actions to check on branding,marketing etc
  • Have a check-point meeting with Metro on June 17 for deciding this.
  • Next step here is involve marketing to help increase nightly ADI for metro
• [MISSED] [lsblakk] (revisiting for Q3) Integrate bugzilla queries and bug lists across release management tools (engineering dashboard, relnotes, nagging, our internal queries, etc.)
• [DONE] Create or drive creation of dynamic per-release tracking report (transfer over from Google Docs)
  • Queries from central DB will be run on every release date, and number noted (visualizations next quarter)
  • https://wiki.mozilla.org/User:Akeybl/Release_Dash fills some of the need
• [DONE] Take B2G process over the 1.0 hump and start scaling for multiple partners, introduce regular cadence and create new partner-requirement process
  • See milestones, landing docs, triage and associated wiki pages, "Framework for Release Success" whitepaper proposal, 1.1hd release planning, checklists, release notes, train model cadence

Smaller, Actionable Goals

• [DONE] [bajaj]Create a forward facing Release Management Wiki page, with a readable index, description of the team and members (for community/PR/recruiting use)
  • https://wiki.mozilla.org/Release_Management/TeamWiki
  • https://etherpad.mozilla.org/relman-team-wiki
• [DONE] [bajaj]Add automatic hg pushes/commits to merge script, expand capability to m-b->m-r as well
  • I can dogfood the existing script on this merge day(Monday) and see how it runs this time and come up with what else we can automate
  • Dogfooded the existing m-a->m-b merge script, made minor edits & lsblakk has tried it as well and hosted has at https://gist.github.com/lsblakk/5568843

• [DONE] [lsblakk] Expand the automatic meeting email script to include sign-offs and post-mortems
• [DONE] [akeybl] Creation of a B2G engineering release calendar
  • https://wiki.mozilla.org/Release_Management/B2G_Deadlines
• [DONE] [lsblakk] Creation of a B2G release notes shared database, get rid of sqlite