mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-22 10:10:06 +00:00
Code Issues Releases Wiki Activity

Modernize Gitlab Bug template

Browse Source
This commit is contained in:
Petr Špaček 2023-12-05 18:29:37 +01:00
parent b77f25446d
commit 6ccb07e09a
1 changed files with 37 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
.gitlab/issue_templates/Bug.md
View File

@ -2,45 +2,62 @@
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please make sure that you make the new issue
confidential!
confidential by clicking the checkbox at the bottom!
-->
### Summary
(Summarize the bug encountered concisely.)
<!-- Concisely summarize the bug encountered. -->
### BIND version used
### BIND version affected
<!--
Make sure you are testing with the **latest** supported version of BIND
for a given branch. Many bugs have been fixed over time!
(Paste the output of `named -V`.)
See https://kb.isc.org/docs/supported-platforms for the current list.
The latest source is available from https://www.isc.org/download/#BIND
Paste the output of `named -V` here.
-->
### Steps to reproduce
(How one can reproduce the issue - this is very important.)
<!--
This is extremely important! Be precise and use itemized lists, please.
Even if a default configuration is affected, please include the full configuration
files _you were testing with_.
Example:
1. Use _attached_ configuration file
2. Start BIND server with command: `named -g -c named.conf ...`
3. Simulate legitimate clients using command `dnsperf -S1 -d legit-queries ...`
4. Simulate attack traffic using command `dnsperf -S1 -d attack-queries ...`
-->
1.
2.
3.
### What is the current *bug* behavior?
(What actually happens.)
<!-- What actually happens. -->
### What is the expected *correct* behavior?
(What you should see instead.)
<!-- What you should see instead. -->
### Relevant configuration files
(Paste any relevant configuration files - please use code blocks (```)
<!-- Paste any relevant configuration files here - please use code blocks (```)
to format console output. If submitting the contents of your
configuration file in a non-confidential Issue, it is advisable to
obscure key secrets: this can be done automatically by using
`named-checkconf -px`.)
configuration file in a non-confidential issue, it is advisable to
obscure key secrets; this can be done automatically by using
`named-checkconf -px`. -->
### Relevant logs and/or screenshots
### Relevant logs
(Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code, as it's very hard to read otherwise.)
<!-- Paste any relevant logs here - please use code blocks (```) to format console
output, logs, and code, as it's very hard to read otherwise. -->
### Possible fixes
(If you can, link to the line of code that might be responsible for the
problem.)
/label ~bug
/label ~Bug