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 Jul 12, 2019 · 88 revisions

Getting the build

Release Schedule

Triage criteria

Definition of severity

S1

  • Key features (or 1st + 2nd level menu features) not `working as intended
  • Regression from user point of view (Definition of “Regression” is as below)
  • Crashes (repro. rate/impacted user # will be considered during Priority discussion)
  • 5% key performance drop (per current metrics: Cold App Launch time + Web Page Loading)

** What is a regression? Basically, if a functionality worked in a previously released version of software stopped working or is working differently and this difference is not a documented change, it’s a regression. We don’t take what caused the regression and/or what platform the software was deployed on into consideration when we decide if a bug is a regression. The cause of regression (e.g., code changes) is irrelevant when we discuss how to fix the regression (or not).

S2

  • 3rd and beyond level menu features not working as intended
  • Major visual impact

S3

  • Minor visual impact

Release blocker: P1 (not necessary S1) will be blockers by default, as a general guideline

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