User:Chianger/draft-bugzilla flag: Difference between revisions

m
All about the ux-b2g flag
m (All about the ux-b2g flag)
Line 36: Line 36:
===ux-b2g Flag===
===ux-b2g Flag===
'''Definition'''
'''Definition'''
* Bulleted list item
Marks UX bugs required for a front-end feature (usually OS-wide) to work properly.
* Bulleted list item
Distinguishes polish and non-blocking UX bugs from blocking UX bugs.
'''Rationale and History'''
The ux-b2g flag was created during the 2.0 release, which was a "UX heavy release:" 2.0 included a lot of UX changes to gestures, animations, the home screen, and so on. This meant that there were numerous OS-wide features -- like the thin, pale blue notifications bar, for example -- that needed to block 2.0+, and that required many UX bugs to be completed (graphics, transitions, animations). Each of these UX bugs needed to block 2.0+ if the finished, front-end feature was to look and behave properly across the OS. The ux-b2g flag was added when these "smaller" bugs were incorrectly marked as "polish," and were actually needed in order for a feature to work.


'''Note'''
'''Note'''
Only members of the Firefox OS UX team and Release Management should set the ux-b2g flag.
Confirmed users
208

edits