Home

Getting the build

Each Github issue has at least 2 labels :

One of the 3 labels to specify its priority (we'll treat "no label" = P2, and add the P2 label from time to time):
- P0: you'd rather delay the release the go without this to be fixed/implemented
- P1: you believe it's very important in the near future
- P2: priority TBD but need to keep it in the radar
One of the vertical labels to specify its vertical domain:
- V-PLATFORM
- V-GAME
- V-TRAVEL
- V-SHOPPING
- V-MSRP
- V-BACKEND

Labels	When to add	Who to tag	Criteria of un-tagging	Who to untag
need metrics	1. Tag on tickets moving to "design phase"; 2.Check regularly for the "design phase" tickets during feature grooming meeting.	PM	BI inputs; DEV confirms (with comments)	BI
need bi audit	1. While removing ticket's 'need metrics' label, tag it if it would require audit; 2. Final overview of the sprint backlog at the end of sprint planning.	BI	BI confirms	BI
need ux/vd	1. Tag on tickets moving to "design phase"; 2. Check regularly for the "design phase" tickets during feature grooming meeting.	PM	UX inputs (with comments or spec attached)	UX
need design audit	1. While removing ticket's 'need UX/VD' label, tag it if it would require audit; 2. Final overview of the sprint backlog at the end of sprint planning.	UX	UX/VD confirms	UX
need size	Precondition: Clearing "need ux/vd", "need _metrics"; 1.Tag on tickets moving to "design phase"; 2. Check regularly for the "design phase" tickets during feature grooming meeting.	PM	DEV inputs	DEV
size = (S, M, L, XL)	While removing ticket's 'need size' label, tag S, M, L, XL accordingly	DEV	NA	NA

Each Github issue can be categorized into the following two types

PM submit P0 features (with a corresponding vertical label) to Github and bring them to Grooming, like the way we are doing today

for bugs, or reopened features/fixes..., QA will assign the vertical label, plus the "need triage" label
PM keeps reviewing all issues within his/her own vertical and decides if it's P0, P1, or P2
- for P0, KEEP "need triage" and add P0 (it becomes a P0 "candidate" at this moment)
- for others, REMOVE "need triage" and add either P1 or P2
during triage we'll review and decide if the "P0 candidate" turns into a confirmed P0, which will be followed during Sprint Planning

each CLOSED issue will get one of the 2 labels to mark its testing status:
- Q-verified
- Q-no need verification

This github repo is public so for security bug please go file on bugzilla.

Choose product "Emerging Markets" and component "Security: Firefox Lite". You can try this link if you have a bugzilla.mozilla.org account logged in: https://bugzilla.mozilla.org/enter_bug.cgi?product=Emerging%20Markets