[mirror_frr.git] / .github / ISSUE_TEMPLATE.md

# HOW TO GET YOUR ISSUE ADDRESSED FASTER

* When reporting a crash provide a backtrace
* When pasting configs, logs, shell output, backtraces, and other large chunks
  of text [use Markdown code blocks](https://github.github.com/gfm/#fenced-code-blocks)
* Include the FRR version; if you built from Git, please provide the commit
  hash
* Write your issue in English

### How to submit an issue
Please use this text as a template and replace text in the sections or remove
the entire section if it does not apply to your issue. For example in case of
a question or feature request, just a description with some example is probably
fine. Also remember to use GitHub Flavored Markdown properly, especially if
posting output or code listings.

### Things you may try first
(put "x" in "[ ]" if you already tried following)
* [ ] Did you check if this is a duplicate issue?
* [ ] Did you test it on the latest FRRouting/frr master branch?

**Related Issue:**
[fill here if applicable]

### Description
[Description of the bug or feature]

### Steps to Reproduce
1. [First Step]
2. [Second Step]
3. [and so on...]

**Expected behavior:**
[What you expected to happen]

**Actual behavior:**
[What actually happened]

### Components
[bgpd, build, doc, isisd, ospfd, etc.]

### Versions
* OS: [name] [version]
* Kernel: [Linux/BSD] [version]
* FRR: [version]

### Attachments
[Attach if applicable. For example log-files, log-lines. etc. etc.]

You're also welcomed to provide us with any other data you think may be useful.

Thanks!
Commit	Line	Data
	1	# HOW TO GET YOUR ISSUE ADDRESSED FASTER
	2
	3	* When reporting a crash provide a backtrace
	4	* When pasting configs, logs, shell output, backtraces, and other large chunks
	5	of text [use Markdown code blocks](https://github.github.com/gfm/#fenced-code-blocks)
	6	* Include the FRR version; if you built from Git, please provide the commit
	7	hash
	8	* Write your issue in English
	9
	10	### How to submit an issue
	11	Please use this text as a template and replace text in the sections or remove
	12	the entire section if it does not apply to your issue. For example in case of
	13	a question or feature request, just a description with some example is probably
	14	fine. Also remember to use GitHub Flavored Markdown properly, especially if
	15	posting output or code listings.
	16
	17	### Things you may try first
	18	(put "x" in "[ ]" if you already tried following)
	19	* [ ] Did you check if this is a duplicate issue?
	20	* [ ] Did you test it on the latest FRRouting/frr master branch?
	21
	22	Related Issue:
	23	[fill here if applicable]
	24
	25	### Description
	26	[Description of the bug or feature]
	27
	28	### Steps to Reproduce
	29	1. [First Step]
	30	2. [Second Step]
	31	3. [and so on...]
	32
	33	Expected behavior:
	34	[What you expected to happen]
	35
	36	Actual behavior:
	37	[What actually happened]
	38
	39	### Components
	40	[bgpd, build, doc, isisd, ospfd, etc.]
	41
	42	### Versions
	43	* OS: [name] [version]
	44	* Kernel: [Linux/BSD] [version]
	45	* FRR: [version]
	46
	47	### Attachments
	48	[Attach if applicable. For example log-files, log-lines. etc. etc.]
	49
	50	You're also welcomed to provide us with any other data you think may be useful.
	51
	52	Thanks!