[nsd-users] NSD 4.1.9 release

[Michael A. Peters]

On 03/17/2016 02:40 AM, Tom Hendrikx wrote:
>
>
> On 16-03-16 12:21, Brett Carr wrote:
>>
>>> On 16 Mar 2016, at 10:13, Jaap Akkerhuis <jaap at nlnetlabs.nl>
>>> wrote:
>>>
>>> Brett Carr writes:
>>>
>>>>
>>>> I would echo Anands endorsement of the nodb mode we use this for
>>>> all of = our TLD secondaries and have found it very efficient and
>>>> stable.
>>>
>>> This discussion raises the question whether we should make this
>>> the default and havng the database optional (for backward
>>> compatibilaty).
>>>
>>> jaap
>>
>> Generally I would say yes this would be a good call however I am
>> always cautious about changing the defaults in software that is
>> important and that people rely on. Not everybody reads mailing lists
>> or software release notes before upgrading, I’d like to think that
>> everybody tests all software before it is changed (we certainly do)
>> however I have worked places where this definitely does not happen.
>> If the default changes then it needs to do this in a seamless manner
>> and it needs to be very clear in the release notes and
>> documentation.
>>
>
> And the version number too. These kind of changes warrant a minor
> version change (i.e. bump to 4.2.x).
>
> I remember a few years ago there was a similar undocumented nsd db
> format change that bit lots of people when code hit production sites.
> Back then using the db was not optional like today. Changes like that
> should not be handled lightly.

Point taken. Hopefully though the configure option is recommended in a 
README file until a new major version is released.