From 932d5c680f7c9cafcb435faaeb4fb576e144dad6 Mon Sep 17 00:00:00 2001 From: Carl <32685696+csagan5@users.noreply.github.com> Date: Mon, 23 Sep 2019 09:20:37 +0200 Subject: [PATCH] Explain how to find Chromium --- .github/ISSUE_TEMPLATE/bug_report.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 6d5f2638..7ad4862c 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -15,9 +15,10 @@ Device model: (example: `SM-G960UZKABST`) Do not report bugs which are not reproducible with latest version -**Can the bug be reproduced with corresponding [Chromium](https://github.com/bromite/chromium/releases) version?** +**Can the bug be reproduced with corresponding Chromium version?** -If yes then report it upstream on [Chromium issue tracker](https://bugs.chromium.org/p/chromium/issues/list) and do not forget to read [Chromium project bug reporting guidelines](https://www.chromium.org/for-testers/bug-reporting-guidelines) first. +Please pick the same version of Chromium as Bromite from here: https://github.com/bromite/chromium/releases +If the bug is reproducible then it might be a configuration issue or an upstream bug. Upstream bugs can be reported on the [Chromium issue tracker](https://bugs.chromium.org/p/chromium/issues/list) and do not forget to read [Chromium project bug reporting guidelines](https://www.chromium.org/for-testers/bug-reporting-guidelines) first. **Is the bug a crash?**