Release Management/Goals/2014Q2: Difference between revisions
< Release Management | Goals
Jump to navigation
Jump to search
Line 24: | Line 24: | ||
* [Bhavana] Help drive Flame updates/builds | * [Bhavana] Help drive Flame updates/builds | ||
** Already having conversations with :francis/:catlee | ** Already having conversations with :francis/:catlee | ||
* [Bhavana] Continue to help on documentation of workflows processes for FxOS | |||
** Guidelines on patch approval/landing process - coming soon!! | |||
** Release notes - Preeti can you help here ? Lets have a wiki up and link it to the main Release Management page | |||
* [Bhavana] Actively continue to participate in bugbashes for FxOS and self-emphasis on dogfooding | |||
** Should be measurable by # of bugs filed | |||
== Personal Development == | == Personal Development == |
Revision as of 06:53, 27 March 2014
Release Management Q2 2014 Goals
Release Management General
Firefox Desktop/Mobile
- [Sylvestre] Release 29 without too much damages
- [Sylvestre] Document most of our workflows / processes
- [Lawrence+Sylvestre] Push on QA tools: code coverage, tools to improve code quality like static analyzers
- [Benjamin] Build a better team wiki landing page
Firefox OS
- [Preeti] Successfully run Phase 1 of dogfooding
- [Preeti] Investigate reducing regressions in FxOS
- [Preeti] Establish a change council for FxOS
- [Bhavana] Work closely with QA and Improve Quality metrics for FxOS (some thoughts below)
- step 1 : Identify existing QA testcases ans ensure 1.3 IOT bugs were included ?
- step 2 : I envision a QA dashboard view with a plot which entails total testcases/time per week
- testcases = regressions+ new feature coverage
- [Bhavana] Automation coverage
- Have a kick-off session with :jgriffin scheduled for 3/27
- I hope to have a good understanding of how much code-coverage we have with the automated tests, what's lacking, identify areas which could be improved upon
- [Bhavana] Drive the necessity of having a good bisection tool
- Often times, we've had situations in FxOS where we cannot pin-point to a bug to identify a fallout
- Not sure, if the existing tools need to be improved or what the core issue is here
- [Bhavana] Help drive Flame updates/builds
- Already having conversations with :francis/:catlee
- [Bhavana] Continue to help on documentation of workflows processes for FxOS
- Guidelines on patch approval/landing process - coming soon!!
- Release notes - Preeti can you help here ? Lets have a wiki up and link it to the main Release Management page
- [Bhavana] Actively continue to participate in bugbashes for FxOS and self-emphasis on dogfooding
- Should be measurable by # of bugs filed
Personal Development
- [Bhavana] - Continue to develop Spanish learning beyond a couple of words I've learnt so far :)
- [Lawrence]
- [Lukas] - achieve over 80% mastery of at least 5 songs on Rocksmith 2014 (guitar playing game with real guitar)
- [Preeti] - blog to get involved with the community. Hope to get a community release manager for B2G
- [Sylvestre] - Continue to go by bike to work
- [Benjamin] - finish reading Agile Product Management with Scrum: Creating Products that Customers Love