Ok, I've done some release prep. @Daniel Stenberg, want to verify and push?
On another note, I see a new PR
https://github.com/c-ares/c-ares/pull/228 recently
came in, in the last 24hrs related to bug
https://github.com/c-ares/c-ares/issues/196
Looks fairly low risk if we wanted to go ahead and include it too.
-Brad
On 10/23/18 5:55 AM, Brad House wrote:
> Heh, sorry, I sent this email then we moved into our new house so time
> got away from me.
>
> I'll work on the release notes, and we'll go ahead and make it
> 1.15.0. I should be
> able to get to that today or tomorrow.
>
> -Brad
>
> On 10/23/18 12:25 AM, Anna Henningsen wrote:
>>
>> Is there anything that I could help with this to make this happen? :)
>>
>> On 10.10.18 23:37, David Hotham wrote:
>>>
>>> I'm not sure whether this project aims for adherence to semantic
>>> versioning; but current master is more than just bug-fixes from
>>> 1.14.0. Eg ARES_OPT_RESOLVCONF is new function.
>>>
>>> So I'm +1 on a new release - why not?! - but if it's to be cut from
>>> the current master then I'd prefer it to be 1.15.0.
>>>
>>>
>>> On 10/10/2018 22:21, Daniel Stenberg wrote:
>>>> On Wed, 10 Oct 2018, Brad House wrote:
>>>>
>>>>> Its been about 8 months since our last release and I think we've
>>>>> accumulated some good bugfixes that would justify a 1.14.1
>>>>> release. There were a couple of files missing for android in the
>>>>> 1.14.0 release tarball that would mean it couldn't be used on that
>>>>> platform. Then some good Windows and Android fixes and query
>>>>> timeout fixes.
>>>>>
>>>>> Thoughts?
>>>>
>>>> I'm all for it!
>>>>
>>>
>
Received on 2018-10-23