The UI bundle now includes a toc in the right hand sidebar, so there's no need to have tocs explicitly at the start of documents.
29 lines
1.1 KiB
Text
29 lines
1.1 KiB
Text
= Reporting Issues
|
|
|
|
When working with Fedora Packaging, you may run across issues
|
|
in packages,
|
|
with the buildsystem,
|
|
with policies or process,
|
|
or with any number of other things.
|
|
Here are some basic guidelines to assist you
|
|
in reporting such issues to the right people.
|
|
|
|
[#where]
|
|
== Where to Report Issues
|
|
|
|
Any issue that requires direct work on Fedora's infrastructure
|
|
should be reported using the
|
|
https://pagure.io/fedora-infrastructure/issues[Fedora Infrastructure issue tracker].
|
|
This would include frozen or failing build systems.
|
|
|
|
For issues within packages, see
|
|
https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to File a Bug].
|
|
This would include typical build errors.
|
|
|
|
Any questions about policy or processes should be reported to the
|
|
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] mailing list.
|
|
This would include questions of spec design, naming conventions or review concerns.
|
|
|
|
If ever you are unsure about which system to use,
|
|
feel free to report to whichever system seems best to you.
|
|
Your report can be redirected as needed.
|