Release Management/Goals/2014Q3: Difference between revisions
< Release Management | Goals
Jump to navigation
Jump to search
Line 53: | Line 53: | ||
* [all] Participate in B2G test days | * [all] Participate in B2G test days | ||
* [Bhavana, Lawrence] <b><platform></b> Create B2G release model proposals and gather feedback for potential changes in 2.2 cycle | * [Bhavana, Lawrence] <b><platform></b> Create B2G release model proposals and gather feedback for potential changes in 2.2 cycle | ||
** We kicked off a discussion | |||
* [Bhavana] <b><platform></b> Figure out what to do with B2G Security Releases | * [Bhavana] <b><platform></b> Figure out what to do with B2G Security Releases | ||
* [Preeti] Create plan for addressing regression backlog | * [Preeti] Create plan for addressing regression backlog |
Revision as of 15:13, 17 July 2014
Release Management Q3 2014 Goals
<platform> denotes goals that are listed on the platform Q3 goals list
Release Management General
- Release Quality - Improve automation / reduce risk of manual errors
- [?] Create automated release checklist (maybe based on ship-it)
- [Sylvestre] Automate manual portions of ship-it
- [DONE] build submission emails
- pull in recent changesets from tbpl
- create new l10n milestone and pull in l10n changesets from dashboard (bug 1035458)
- auto populate branch (tied to version)
- auto populate partials
- determine if dashboard check is useful
- [Lukas] Fully automate Product-Details
- 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)
- Release Quality - Find issues earlier
- [Pranav] Release Readiness Dashboard
- Get dashboard into a state where the team can use it on a daily basis
- Complete implementation of Talos, Telemetry, and Socorro data sources
- Create initial views and indexes for performance and stability
- [Lawrence] Add new repository hooks
- Create checkIID hook to catch required IIDL bumps
- Create string freeze hook to catch string changes on Aurora and Beta
- Investigate RIL hook to catch RIL changes on Aurora and later
- Communication
- [Lukas] Create relman blog release.mozilla.org (bug 1029160)
- [Sylvestre] Feed the relman blog with the changelogs
- [?] <platform> Create Release Notes proposal for a revamped template including formatting, new categories, optional image/video, and handling of point releases
- This improves public perception of the product and also helps our enterprise sysadmins have the info they need to keep using Firefox in large deployments
- Continue to refine team wiki
- [Ben] Simplify landing page
- [Sylvestre, Lawrence] Refine Aurora, Beta, and ESR documentation
- [Ben] Refine team information
- Expand contributor involvement
- [Lukas] Investigate requirements for new contributors (NDA, sec access)
- [?] Define contributor pathways
- Triage of Desktop, Mobile, B2G, Platform, Services (?) bugs
- [Ben] Create onboarding documentation for new contributors on wiki including week-by-week breakdown
Firefox Desktop/Mobile
- [Lukas] <platform> Continuing ESR
- Finalize if ESR will be ongoing
- Devise a plan to manage ESR releases (can this be community based?)
- [Lukas] <platform> Throttling improvements - continue to collect data for FF31, then implement updated SOP
- This will get a faster uptake on new features in product release - great for press/marketing efforts to get more Mozillians
- [Sylvestre] Determine whether we can make release-drivers archive public
- [Lawrence] <platform> Create and document process for feature fast tracking
- Increased user delight, at a more rapid pace, when there are exciting features that could benefit from a specific date/timed release in conjunction with marketing/pr
Firefox OS
- [all] Participate in B2G test days
- [Bhavana, Lawrence] <platform> Create B2G release model proposals and gather feedback for potential changes in 2.2 cycle
- We kicked off a discussion
- [Bhavana] <platform> Figure out what to do with B2G Security Releases
- [Preeti] Create plan for addressing regression backlog
Special Projects
- [Bhavana] Get l10n strings changes going-in for Hindi
- [Bhavana] Take some initiative related to community events, MoZRep involvement
- Signed up to be a mentor for TechWomen 2014 (Will know by July end if that works out)
- [Lukas] Ascend Project
- develop curriculum
- select participants for first pilot
- launch first pilot
- [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
- Incorporate static analyzer in builds and report on diffs
- Better tests
- Coding style
- [Lawrence] Determine next steps for Manager Hacking program
- [Preeti] Work with contributors in India to get Mozilla Location Services (MLS) data from various cities
Personal Development
- [Bhavana]
- [Lawrence] Continue French lessons with DuoLingo, achieve level 10 (currently level 8)
- [Lukas] Reading as many books (in their entirety) as possible on this vacation (previous vacation reached 8)
- [Preeti] Learn Zumba, pass basic class and progress to intermediate
- [Sylvestre] Release a baby!
- [Benjamin] Kick Off Reading Peopleware: Productive Projects and Teams, Third Edition
- [Pranav]