You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/rocky/bu_support.md
+4-1
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,9 @@ title: Getting Community Help & Support
4
4
5
5
The Rocky Linux Project has several places where users can find community support, depending on the nature of issue.
6
6
7
+
!!! note
8
+
This is for general support of Rocky Linux and is not meant for bug reporting. Please see our [Reporting Bugs and RFE's page](bugs.md) for more information.
9
+
7
10
## Rocky Linux (core distribution)
8
11
9
12
Core distribution community support can be obtained at the following locations:
@@ -16,7 +19,7 @@ Core distribution community support can be obtained at the following locations:
16
19
17
20
## Rocky Linux Infrastructure and Services
18
21
19
-
Rocky Linux Infrastructure have responsibility over several areas. Support or questions can be asked at any of the following:
22
+
Rocky Linux Infrastructure have responsibility over several areas, such as mirror manager and Mattermost. Support or questions that pertain only to the infrastructure managed by the project can be asked at any of the following:
Copy file name to clipboardexpand all lines: docs/rocky/bugs.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -8,18 +8,18 @@ The Rocky Linux Project has several ways of reporting issues or requesting enhan
8
8
9
9
### Bugs
10
10
11
+
!!! note
12
+
The bug tracker is **not** meant for general support questions. Do not be surprised if a maintainer closes the bug report immediately if it's found to be a general question rather than an actual bug report.
13
+
11
14
Bugs are an inevitable part of any Linux distribution. Users may find problems and want a way to report the bug.
12
15
13
-
All bug reports (which includes some packages from Special Interest Groups) should be reported at our [Bug Tracker](https://bugs.rockylinux.org).
16
+
All bug reports should be reported at our [Bug Tracker](https://bugs.rockylinux.org).
14
17
15
18
When reporting bugs, ensure you have read the [Bug Tracker Guidelines](../guidelines/bug_tracker_guidelines.md) so you can make a proper bug report.
16
19
17
20
!!! note
18
21
You may be asked to reproduce the issue on Red Hat Enterprise Linux. If the issue is reproducible on RHEL, you are encouraged to also open a bug report at the [Red Hat Jira](https://issues.redhat.com). The assignee on your bug report can do this for you also if you wish.
19
22
20
-
!!! note
21
-
The bug tracker is not meant for general support questions. Do not be surprised if a maintainer closes the bug report immediately if it's found to be a general support question rather than an actual bug report.
22
-
23
23
### RFE (Request for Enhancement)
24
24
25
25
Requests for Enhancements to packages[^1] are typically handled at the [Bug Tracker](https://bugs.rockylinux.org). In some cases, this may not apply. A Special Interest Group may ask that an RFE be submitted elsewhere. See the SIG section later in this page.
0 commit comments