From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: bind 9.12.0
Date: Wed, 24 Jan 2018 14:09:20 +0100 [thread overview]
Message-ID: <97ad7b33-a79a-f1dc-7733-2d8c7315413d@ipfire.org> (raw)
In-Reply-To: <1516797732.3647.213.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
Hi,
On 24.01.2018 13:42, Michael Tremer wrote:
> Hi,
>
> since we don't use named the list of changes is somewhat small-ish.
>
> I don't think we need to chase after every single release for bind as long as it
> isn't a security one. So a patched 9.11.x is fine with me as long as it is
> supported upstream.
Full ACK. I was a bit puzzled about this shortcoming update and the long
lists of changes indicate extensive adjustments.
[By the way: It happened as I thought. It won't build with our current
settings, 'Devel' just stopped. I'll give him a pause...]
> Anyways since this is a .0 release, it probably makes sense to wait a little
> until someone else has found the nasty bugs.
;-)
Ok, that is similar to my - second - thought.
Thanks for quick answer! ;-)
Best,
Matthias
>
> Best,
> -Michael
>
> On Wed, 2018-01-24 at 12:49 +0100, Matthias Fischer wrote:
>> Hi,
>>
>> About a week ago I uploaded 'bind 9.11.2-p1', today version '9.12.0' was
>> released. Hm.
>>
>> For details see:
>> http://ftp.isc.org/isc/bind9/9.12.0/RELEASE-NOTES-bind-9.12.0.html
>>
>> "BIND 9.12.0 is a new feature release of BIND. This document summarizes
>> new features and functional changes that have been introduced on this
>> branch, as well as features that have been deprecated or removed."
>>
>> Could someone please take a look at these new/removed features and
>> changes? I'm not sure whether we can and want to implement this update
>> in view of the extensive changes.
>>
>> Best,
>> Matthias
>
prev parent reply other threads:[~2018-01-24 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 11:49 Matthias Fischer
2018-01-24 12:42 ` Michael Tremer
2018-01-24 13:09 ` Matthias Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97ad7b33-a79a-f1dc-7733-2d8c7315413d@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox