~samiam/MaraDNS

ref: 3.5.0002 MaraDNS/deadwood-github/bug.reporting.policy -rw-r--r-- 1.8 KiB View raw
db09084f — Sam Trenholme MaraDNS release 3.5.0002 3 months ago
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Deadwood is a released and stable program.  The only bugs I am fixing 
right now are security bugs and simple typo bugs.  Some notes:

* Valgrind-reported memory leaks can always be reported.  Valgrind-reported
	errors are only valid if Deadwood is compiled with -DVALGRIND_NOERRORS

* The only officially supported OSes are Windows 7 and CentOS 6.
	OS-specific issues such as startup, daemonizing, sysloggin, and 
	/etc/resolv.conf setup are only supported on these two OSes.

* Bugs need to be reported in GitHub, not to my email account nor
	as blog comments.  

* Bugs reporting Deadwood crashes will probably be marked "unreproducible" 
	unless either a stack trace (or core dump if the program was 
	compiled with '-g' to enable debugging symbols) or a recipe to 
	reproduce the crash is provided.

* Bugs involving Deadwood recursively resolving a name different than
	other DNS servers when the domain is misconfigured will probably
	not be fixed. 

* Bugs involving RFCs with a date more recent than July of 2010 will 
	probably not be fixed. If the RFC number is higher then 5900 or so, 
	or has a date in the top of the RFC more recent than July 2010,
	I will probably ignore it.

Welcome to the world of open source economics: The code is free, but
there is no guarantee of support, since there is no money on the table
compelling one to support the program.

Here are some bugs I will not fix:

https://github.com/samboy/MaraDNS/issues/8
https://github.com/samboy/MaraDNS/issues/12
https://github.com/samboy/MaraDNS/issues/14
https://github.com/samboy/MaraDNS/issues/26 

I mark bugs claiming that various parameters do not always work as
expected as “WORKSFORME” unless one includes a script to reproduce
the issue in the bug report; I do run automated tests to make sure pretty
much all Deadwood parameters work correctly every time I make a Deadwood
release.