Confirm
976
edits
Changes
no edit summary
=Release Uplift=
* Must be a part of a known-issue respin or NPTOB (not part of the build) config changes needed to support build infra
<Italic><b>note: This section is still in progress</b></Italic>
=Firefox OS gaia uplifts=
==approval-gaia-v1.4==
* As we've moved on from active feature development to stabilization mode on 3/14 for the 1.4 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) ===
* any non-blocking bug that has a high user impact
* 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
* If you a requesting approval on a gaia patch that needs to land on 1.4 that
** Set approval-gaia-v1.4: ? and making sure to fill the populated set of questions [Approval Request Comment] that come up on the attachment
** Note, for v1.4 - Non-blocking gaia approvals will not be approved after 4/11
[[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 or 1.4 branch, set request approval-gaia-1.3: ? on patch attachment and fill in the approval request comment
=== Guidelines on approval comments ===
* [Bug caused by] (feature/regressing bug #): If you this is a fallout from a feature/bug, a backout please state the reason along with the bug number
* [User impact] if declined: In addition to the STR reported in the bug if you can explain on a deeper level aspect of how an end user would be impacted with/without your change
=Special cases=
