Changes

Jump to: navigation, search

Release Management/Uplift rules

314 bytes removed, 02:19, 7 February 2015
fxos edits
* Must be a part of a known-issue respin or NPTOB (not part of the build) config changes needed to support build infra
=Firefox OS gaia /gecko uplifts= ==approval-gaia-v2.x=/approval-gecko-b2g37==* For any gaia/gecko change's landing on the 2.x release, please request approval to land* Please note, the closer we try to wrap up stabilization mode the more stricter we'd be on taking any changes
==approval-gaia-v2.x==
* As we've moved on from active feature development to stabilization mode on 6/9 for the 2.0 Release, we understand that their may be issues that don't necessarily block but can make a strong case for uplifts (refer to the criteria below).
* For such cases, we request folks to request approvals, which may be granted depending on the risk/reward analysis
* Please note, the closer we try to wrap up stabilization mode the more stricter we'd be on taking any non-needed changes and absolutely no changes in the last sprint of stabilization
=== Criteria to request approval (Guidelines) ===
* Patch must be landed and Resolved on master/central* any non-blocking bug that has a high user impact* String changes may not be approved after the string freeze dealine
* a low risk Polish change : Visual polish - colors, sizes, icons, alignment, etc
* functional-polish: Example, Notification tray displaying that your microphone is active, but onclick does not do do anything. Ideally it should take to to microphone settings if I wanted to play with it..It's not really a bug, but it could be better. And it requires code changes, not just visual work.
* papercuts: It's for issues found during dogfooding/testing that are visually or functionally annoying or otherwise sub-par, but not enough to block the release
* Performance/crash-fixes : Depending on the risk evaluation and the reward we get ny uplifting these will be highly considered depending on where we are in the release cycle* If you a requesting approval on a gaia /gecko patch that needs to land on 2.0 x that** Set approval-gaia-v2.0x: ? and making sure to fill the populated set of questions [Approval Request Comment] that come up on the attachment
[[File:Gaia-approval.png|800px|center]]
==approval-gaia-v1.3==* Any bug that needs to land on the 1.3 branch needs to get approval (even blockers : 1.3+)* Once your patch has landed on master, set request approval-gaia-1.3: ? on patch attachment and fill in the approval request comment
=Special cases=
Bhavana
Confirm
976
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1054426"

Navigation menu