Browse code

ISSUE_TEMPLATE/bug_report.md: list lsb_release -a in comments for OS details

Daniel-Constantin Mierla authored on 10/08/2021 07:16:17 • GitHub committed on 10/08/2021 07:16:17
Showing 1 changed files
... ...
@@ -95,7 +95,7 @@ If you found a solution or workaround for the issue, describe it. Ideally, provi
95 95
 
96 96
 <!--
97 97
 Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
98
-Kernel details (output of `uname -a`)
98
+Kernel details (output of `lsb_release -a` and `uname -a`)
99 99
 -->
100 100
 
101 101
 ```
Browse code

Update issue templates

Henning Westerholt authored on 27/09/2018 13:14:50
Showing 1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,103 @@
1
+---
2
+name: Bug report
3
+about: Create a report to help us improve
4
+
5
+---
6
+
7
+<!--
8
+Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
9
+
10
+If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
11
+
12
+  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
13
+
14
+If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
15
+
16
+  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
17
+
18
+Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
19
+
20
+If there is no content to be filled in a section, the entire section can be removed.
21
+
22
+You can delete the comments from the template sections when filling.
23
+
24
+You can delete next line and everything above before submitting (it is a comment).
25
+-->
26
+
27
+### Description
28
+
29
+<!--
30
+Explain what you did, what you expected to happen, and what actually happened.
31
+-->
32
+
33
+### Troubleshooting
34
+
35
+#### Reproduction
36
+
37
+<!--
38
+If the issue can be reproduced, describe how it can be done.
39
+-->
40
+
41
+#### Debugging Data
42
+
43
+<!--
44
+If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
45
+local variables and the list of the code at the issue location.
46
+
47
+  gdb /path/to/kamailio /path/to/corefile
48
+  bt full
49
+  info locals
50
+  list
51
+
52
+If you are familiar with gdb, feel free to attach more of what you consider to
53
+be relevant.
54
+-->
55
+
56
+```
57
+(paste your debugging data here)
58
+```
59
+
60
+#### Log Messages
61
+
62
+<!--
63
+Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
64
+-->
65
+
66
+```
67
+(paste your log messages here)
68
+```
69
+
70
+#### SIP Traffic
71
+
72
+<!--
73
+If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
74
+-->
75
+
76
+```
77
+(paste your sip traffic here)
78
+```
79
+
80
+### Possible Solutions
81
+
82
+<!--
83
+If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
84
+-->
85
+
86
+### Additional Information
87
+
88
+  * **Kamailio Version** - output of `kamailio -v`
89
+
90
+```
91
+(paste your output here)
92
+```
93
+
94
+* **Operating System**:
95
+
96
+<!--
97
+Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
98
+Kernel details (output of `uname -a`)
99
+-->
100
+
101
+```
102
+(paste your output here)
103
+```