<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>> From: peter.van.dijk@netherlabs.nl<br><div>> Date: Wed, 10 Oct 2012 16:25:56 +0200<br>> To: pdns-users@mailman.powerdns.com; pdns-dev@mailman.powerdns.com<br>> Subject: [Pdns-users] IMPORTANT: please help us test the uncommon backends!<br>> <br>> Hello,<br>> <br>> occasionally, a change in PowerDNS breaks one or more backends. Often, this goes unnoticed until a user complains, months later, often even after a full release of PowerDNS.<br>> <br>> Right now, we test a bunch of backends after every commit:<br>> - bind<br>> - gmysql<br>> - gsqlite3<br>> - gpgsql<br>> - tinydns<br>> - opendbx<br>> <br>> Breakage in any other backend will go unnoticed by our tests (although there are plenty of pipe users who frequently update from SVN).<br>> <br>> If you are using any backend not in this list, please talk to me about adding it to our testing setup. We love supporting all these backends but manual testing is not an option for us. I'm not asking for you to submit full testing suites to us - for many backends, I simply do not have the time to find out how to even get them set up.<br>> <br>> Be aware that if we find broken backends that have been broken for at least one release without anyone complaining, we WILL remove them.<br>> <br>> Please respond :)<br><br>We cannot live without the "oracle" (not "goracle") backend; if it weren't for it, PowerDNS would not be a viable option.<br><br>If you can tell us exactly what it is that you would need to keep supporting it, we might be able to produce it.<br><br>We currently have pdns 3.1 running with the "oracle" backend. Attempts to get it running with "opendbx" and "goracle" failed after much trial and error.<br></div> </div></body>
</html>