Release Management Q4 2014 Goals

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

Release Management General

[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)

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

[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?)

[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

[Bhavana]
[Lawrence]
[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
[Preeti]
[Sylvestre]
[Benjamin]