From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Kang Kai <Kai.Kang@windriver.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] bind: 9.10..3-P3 -> 9.10.5-P3
Date: Fri, 21 Jul 2017 14:45:02 +0300 [thread overview]
Message-ID: <0a89d9fe-3156-9643-fa11-d5df868da586@linux.intel.com> (raw)
In-Reply-To: <b68e4ea9-6d93-f9c5-7e2a-ca0664894c6e@windriver.com>
On 07/21/2017 09:37 AM, Kang Kai wrote:
> It doesn't mention that api changes in 9.11 from release notes pages of
> 9.11.0rc1 and 9.11.0.
>
> https://kb.isc.org/article/AA-01409
> https://kb.isc.org/article/AA-01432/81/BIND-9.11.0-Release-Notes.html
>
>
> But it suggests not to use 9.11 until the second maintenance
> release(9.11.2 if I understand correctly) for production systems:
>
> | We recommend that administrators run one of our older, stable
> branches, such as a 9.9 or 9.10-based release on larger-scale critical
> production systems, while testing the new 9.11 branch until the second
> maintenance release.
>
> https://www.isc.org/downloads/bind/bind-9-11-new-features/
Fair enough, let's stick with 9.10 for now then.
Alex
prev parent reply other threads:[~2017-07-21 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 1:25 [PATCH 0/1] bind: 9.10..3-P3 -> 9.10.5-P3 kai.kang
2017-07-12 1:25 ` [PATCH 1/1] " kai.kang
2017-07-12 8:40 ` [PATCH 0/1] " Kang Kai
2017-07-17 13:38 ` Alexander Kanavin
2017-07-18 2:04 ` Kang Kai
2017-07-18 19:14 ` Alexander Kanavin
2017-07-18 21:08 ` Khem Raj
2017-07-19 13:05 ` Alexander Kanavin
2017-07-21 6:37 ` Kang Kai
2017-07-21 11:45 ` Alexander Kanavin [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=0a89d9fe-3156-9643-fa11-d5df868da586@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=Kai.Kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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