From 5b2ecb8bbabb7b8346f488e860ac235ebe22a673 Mon Sep 17 00:00:00 2001 From: Jan Kaluza Date: Jul 18 2019 05:14:09 +0000 Subject: Issue #145: Add more explanation for MBS and DNF issues to Reporting Issue document. Signed-off-by: Jan Kaluza --- diff --git a/modules/ROOT/pages/reporting-issues.adoc b/modules/ROOT/pages/reporting-issues.adoc index b318ed4..04b1858 100644 --- a/modules/ROOT/pages/reporting-issues.adoc +++ b/modules/ROOT/pages/reporting-issues.adoc @@ -6,5 +6,6 @@ There is a main issue tracker to report general issues. However, if you know you Specific components: -* https://pagure.io/fm-orchestrator/issues[MBS (Module Build Service) issue tracker] — Issues regarding MBS specifically. +* https://pagure.io/fm-orchestrator/issues[MBS (Module Build Service) issue tracker] — Issues regarding MBS upstream project specifically. If your issue or RFE changes the syntax or semantics of the MBS input or the MBS output (RPMs built in a module or resulting modular metadata), it does belong to https://pagure.io/modularity/issues[**General Modularity issue tracker**]. If your issue is related to particular module build in Fedora infrastructure, it belongs to https://pagure.io/fedora-infrastructure/[Fedora Infrastructure issue tracker]. Any other MBS issue can be filed in the MBS issue tracker. * https://github.com/fedora-modularity/libmodulemd/issues[libmodulemd issue tracker] — Issues regarding the modulemd specification and the libmodulemd library. +* https://src.fedoraproject.org/rpms/dnf[DNF issue tracker] — Issues regarding the "dnf module" command.