Adding upstream version 124.0.1.upstream/124.0.1

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 37 insertions, 0 deletions

diff --git a/docs/bug-mgmt/guides/bug-pipeline.rst b/docs/bug-mgmt/guides/bug-pipeline.rst
new file mode 100644
index 0000000000..a70adb0464
--- /dev/null
+++ b/docs/bug-mgmt/guides/bug-pipeline.rst
@@ -0,0 +1,37 @@
+Bug pipeline
+============
+
+For Firefox quality, Mozilla has different processes to report defects. In parallel, over the years, Mozilla developed many tools around bug management.
+
+.. mermaid::
+
+     graph TD
+         classDef tool fill:#f96;
+
+         Community --> B(bugzilla.mozilla.org)
+         QA --> B
+         Foxfooding --> B
+         Fuzzing --> B
+         SA[Static/Dynamic analysis] --> B
+         P[Performance monitoring] --> B
+         Y[Test automation] --> B
+         Z[Crash detection] --> B
+         B --> C{Bug update}
+         C --> D[Metadata improvements]
+         C --> E[Component triage]
+         C --> F[Test case verification]
+         F --> BM{{Bugmon}}:::tool
+         F --> MR{{Mozregression}}:::tool
+
+         D --> AN{{Autonag}}:::tool
+         E --> BB{{bugbug}}:::tool
+         D --> BB
+
+More details
+------------
+
+* :ref:`Fuzzing`
+* `Autonag <https://wiki.mozilla.org/Release_Management/autonag#Introduction>`_ - `Source <https://github.com/mozilla/relman-auto-nag/>`_
+* `Bugbug <https://github.com/mozilla/bugbug>`_ - `Blog post about triage <https://hacks.mozilla.org/2019/04/teaching-machines-to-triage-firefox-bugs/>`_ / `Blog post about CI <https://hacks.mozilla.org/2020/07/testing-firefox-more-efficiently-with-machine-learning/>`_
+* `Bugmon <https://hacks.mozilla.org/2021/01/analyzing-bugzilla-testcases-with-bugmon/>`_ - `Source <https://github.com/MozillaSecurity/bugmon>`_
+* `Mozregression <https://mozilla.github.io/mozregression/>`_ - `Source <https://github.com/mozilla/mozregression>`_