On Thu, Sep 29, 2016 at 7:46 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Tue, 27 Sep 2016, David Drysdale via c-ares wrote:
>
>>> That made me think. Do you think we should bump the version number for
>>> the pending release to 1.12.0 because of this new ARES_OPT_NOROTATE value?
>
>
>> That probably makes sense -- I think the change is generally
>> back-compatible, but there is a slight API extension (in that a new bit can
>> now show up in the optmask).
>
>
> Then let's do that.
From another thread: presumably this also needs a CARES_VERSION_INFO update?
(Maybe move it along by 2 to allow for the fact that 1.11 didn't get a
version bump).
More generally, I wonder if it might be worth writing down a checklist of what's
involved in a new release?
> Oh and btw, I think you forgot to add a ARES_OPT_NOROTATE description to
> ares_init_options.3 (we actually lack docs for several other OPTs too).
Oops, pull request incoming...
> --
>
> / daniel.haxx.se
Received on 2016-09-29