Browse code

Delete ISSUE_TEMPLATE.md

delete issue template file, not needed anymore after customized version

Henning Westerholt authored on 27/09/2018 13:16:48 • GitHub committed on 27/09/2018 13:16:48
Showing 1 changed files
1 1
deleted file mode 100644
... ...
@@ -1,103 +0,0 @@
1
-<!--
2
-Kamailio Project uses GitHub Issues only for bugs in the code or feature requests.
3
-
4
-If you have questions about using Kamailio or related to its configuration file,
5
-ask on sr-users mailing list:
6
-
7
-  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
8
-
9
-If you have questions about developing extensions to Kamailio or its existing
10
-C code, ask on sr-dev mailing list
11
-
12
-  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
13
-
14
-Please try to fill this template as much as possible for any issue. It helps the
15
-developers to troubleshoot the issue.
16
-
17
-If you submit a feature request (or enhancement), you can delete the text of
18
-the template and only add the description of what you would like to be added.
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
-### Description
27
-
28
-<!--
29
-Explain what you did, what you expected to happen, and what actually happened.
30
-
31
-### Troubleshooting
32
-
33
-#### Reproduction
34
-
35
-<!--
36
-If the issue can be reproduced, describe how it can be done.
37
-
38
-#### Debugging Data
39
-
40
-<!--
41
-If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
42
-local variables and the list of the code at the issue location.
43
-
44
-  gdb /path/to/kamailio /path/to/corefile
45
-  bt full
46
-  info locals
47
-  list
48
-
49
-If you are familiar with gdb, feel free to attach more of what you consider to
50
-be relevant.
51
-
52
-```
53
-(paste your debugging data here)
54
-```
55
-
56
-#### Log Messages
57
-
58
-<!--
59
-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).
60
-
61
-```
62
-(paste your log messages here)
63
-```
64
-
65
-#### SIP Traffic
66
-
67
-<!--
68
-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).
69
-
70
-```
71
-(paste your sip traffic here)
72
-```
73
-
74
-### Possible Solutions
75
-
76
-<!--
77
-If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
78
-
79
-### Additional Information
80
-
81
-  * **Kamailio Version** - output of `kamailio -v`
82
-
83
-```
84
-(paste your output here)
85
-```
86
-
87
-* **Operating System**:
88
-
89
-<!--
90
-Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
91
-Kernel details (output of `uname -a`)
92
-
93
-```
94
-(paste your output here)
95
-```
Browse code

update mailing list URL

Victor Seva authored on 23/08/2018 14:59:11
Showing 1 changed files
... ...
@@ -4,12 +4,12 @@ Kamailio Project uses GitHub Issues only for bugs in the code or feature request
4 4
 If you have questions about using Kamailio or related to its configuration file,
5 5
 ask on sr-users mailing list:
6 6
 
7
-  * http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
7
+  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
8 8
 
9 9
 If you have questions about developing extensions to Kamailio or its existing
10 10
 C code, ask on sr-dev mailing list
11 11
 
12
-  * http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
12
+  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
13 13
 
14 14
 Please try to fill this template as much as possible for any issue. It helps the
15 15
 developers to troubleshoot the issue.
Browse code

core: github issue template - sections for log messages and sip traffic

Daniel-Constantin Mierla authored on 16/01/2017 15:34:54
Showing 1 changed files
... ...
@@ -17,6 +17,8 @@ developers to troubleshoot the issue.
17 17
 If you submit a feature request (or enhancement), you can delete the text of
18 18
 the template and only add the description of what you would like to be added.
19 19
 
20
+If there is no content to be filled in a section, the entire section can be removed.
21
+
20 22
 You can delete the comments from the template sections when filling.
21 23
 
22 24
 You can delete next line and everything above before submitting (it is a comment).
... ...
@@ -30,14 +32,15 @@ Explain what you did, what you expected to happen, and what actually happened.
30 32
 
31 33
 ### Troubleshooting
32 34
 
33
-<!--
34
-
35 35
 #### Reproduction
36 36
 
37
+<!--
37 38
 If the issue can be reproduced, describe how it can be done.
39
+-->
38 40
 
39
-#### Backtrace
41
+#### Debugging Data
40 42
 
43
+<!--
41 44
 If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
42 45
 local variables and the list of the code at the issue location.
43 46
 
... ...
@@ -46,10 +49,34 @@ local variables and the list of the code at the issue location.
46 49
   info locals
47 50
   list
48 51
 
49
-If you are familiar with gdb, feel free to attach more of what you condier to
52
+If you are familiar with gdb, feel free to attach more of what you consider to
50 53
 be relevant.
51 54
 -->
52 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
+
53 80
 ### Possible Solutions
54 81
 
55 82
 <!--
Browse code

core: github issue template with more details regading operating system

Daniel-Constantin Mierla authored on 16/01/2017 15:24:11
Showing 1 changed files
... ...
@@ -67,7 +67,7 @@ If you found a solution or workaround for the issue, describe it. Ideally, provi
67 67
 * **Operating System**:
68 68
 
69 69
 <!--
70
-Details about the operating system, the type: tMacOS, Linux, xBSD, Solaris, ...;
70
+Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
71 71
 Kernel details (output of `uname -a`)
72 72
 -->
73 73
 
Browse code

core: added github new issue template

Daniel-Constantin Mierla authored on 16/01/2017 15:17:53
Showing 1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,76 @@
1
+<!--
2
+Kamailio Project uses GitHub Issues only for bugs in the code or feature requests.
3
+
4
+If you have questions about using Kamailio or related to its configuration file,
5
+ask on sr-users mailing list:
6
+
7
+  * http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
8
+
9
+If you have questions about developing extensions to Kamailio or its existing
10
+C code, ask on sr-dev mailing list
11
+
12
+  * http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
13
+
14
+Please try to fill this template as much as possible for any issue. It helps the
15
+developers to troubleshoot the issue.
16
+
17
+If you submit a feature request (or enhancement), you can delete the text of
18
+the template and only add the description of what you would like to be added.
19
+
20
+You can delete the comments from the template sections when filling.
21
+
22
+You can delete next line and everything above before submitting (it is a comment).
23
+-->
24
+
25
+### Description
26
+
27
+<!--
28
+Explain what you did, what you expected to happen, and what actually happened.
29
+-->
30
+
31
+### Troubleshooting
32
+
33
+<!--
34
+
35
+#### Reproduction
36
+
37
+If the issue can be reproduced, describe how it can be done.
38
+
39
+#### Backtrace
40
+
41
+If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
42
+local variables and the list of the code at the issue location.
43
+
44
+  gdb /path/to/kamailio /path/to/corefile
45
+  bt full
46
+  info locals
47
+  list
48
+
49
+If you are familiar with gdb, feel free to attach more of what you condier to
50
+be relevant.
51
+-->
52
+
53
+### Possible Solutions
54
+
55
+<!--
56
+If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
57
+-->
58
+
59
+### Additional Information
60
+
61
+  * **Kamailio Version** - output of `kamailio -v`
62
+
63
+```
64
+(paste your output here)
65
+```
66
+
67
+* **Operating System**:
68
+
69
+<!--
70
+Details about the operating system, the type: tMacOS, Linux, xBSD, Solaris, ...;
71
+Kernel details (output of `uname -a`)
72
+-->
73
+
74
+```
75
+(paste your output here)
76
+```