Skip to content
This repository has been archived by the owner on Jul 5, 2021. It is now read-only.
Wesley Huang edited this page Nov 13, 2019 · 88 revisions

Getting the build

Release Schedule

Triage criteria

Github issues should have at least 2 labels :

  • Each Github issue should have 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
  • Each Github issue should have one of the vertical labels to specify its vertical domain:

    • V-PLATFORM
    • V-GAME
    • V-TRAVEL
    • V-SHOPPING
    • V-MSRP
    • V-BACKEND

Planning and Development

Each Github issue can be categorized into the following two types

1. New Feature

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

2. Others (!=New Feature)

  • 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

Testing

  • each CLOSED issue will get one of the 2 labels to mark its testing status:

    • Q-verified
    • Q-no need verification

Reporting issues

Bug template

  • Steps to reproduce
  • Actual Result (incl. Video or screenshot)
  • Expected Result (incl. Video or screenshot)
  • Reproduction rate, IsIt Regression?
  • FirefoxLite version, Device name
  • Android/WebView version
  • Additional info: for instance, 3rd party app's behavior on the same website

Reporting security bugs

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