Re: patch release tomorrow

2016-08-09 Thread K. Frank
Hello Steve and Daniel! On Mon, Aug 8, 2016 at 2:43 PM, Steve Holme wrote: > On Sun, 7 Aug 2016, Daniel Stenberg wrote: > ... > I understand your view point and I won't argue with that - its half a dozen > of one and 6 of the other in my opinion. Which weighs more,

Re: patch release tomorrow

2016-08-09 Thread Dan Fandrich
On Tue, Aug 09, 2016 at 12:13:02PM +0200, Daniel Stenberg wrote: > On Tue, 9 Aug 2016, Dan Fandrich wrote: > > >I wouldn't mind seeing CURL_STRICTER set automatically whenever > >CURL_NO_OLDIES is set. The latter is used by people to ensure that their > >code is forward-compatible with libcurl

Re: patch release tomorrow

2016-08-09 Thread Daniel Stenberg
On Tue, 9 Aug 2016, Dan Fandrich wrote: I wouldn't mind seeing CURL_STRICTER set automatically whenever CURL_NO_OLDIES is set. The latter is used by people to ensure that their code is forward-compatible with libcurl and the CURL_STRICTER changes really fall into the same bucket. I agree, I

Re: patch release tomorrow

2016-08-09 Thread Dan Fandrich
On Tue, Aug 02, 2016 at 11:27:17PM +0200, Daniel Stenberg wrote: > On Tue, 2 Aug 2016, Richard Gray wrote: > >>Possibly most notable: we're reverting the change that modified the > >>CURL, CURLM and CURLSH types and they go back to be 'void *' unless you > >>define CURL_STRICTER before including

RE: patch release tomorrow

2016-08-08 Thread Steve Holme
On Sun, 7 Aug 2016, Daniel Stenberg wrote: > > I also appreciate this is a little subjective but I would have thought > > adding support for NTLM with mbedTLS is also a new functionality - > > previously NTLM wasn't supported with mbedTLS so I wouldn't class that as a > > bug fix. > > That's

RE: patch release tomorrow

2016-08-07 Thread Daniel Stenberg
On Sun, 7 Aug 2016, Steve Holme wrote: I also appreciate this is a little subjective but I would have thought adding support for NTLM with mbedTLS is also a new functionality - previously NTLM wasn't supported with mbedTLS so I wouldn't class that as a bug fix. That's of course a matter of

RE: patch release tomorrow

2016-08-07 Thread Steve Holme
> On Sat, 6 Aug 2016, Daniel Stenberg wrote: > > I've already push Bill's mbedTLS NTLM addition and I'm hoping to get > > Sergei's LDAP change pushed this weekend (although I might to step up and > > finish the documentation side off!). Is this enough for a major bump as I > > probably need to

Re: patch release tomorrow

2016-08-07 Thread Sergei Nikulov
2016-08-06 22:25 GMT+03:00 Daniel Stenberg : > On Sat, 6 Aug 2016, Steve Holme wrote: > >> I've already push Bill's mbedTLS NTLM addition and I'm hoping to get >> Sergei's LDAP change pushed this weekend (although I might to step up and >> finish the documentation side off!). Is

RE: patch release tomorrow

2016-08-06 Thread Daniel Stenberg
On Sat, 6 Aug 2016, Steve Holme wrote: I've already push Bill's mbedTLS NTLM addition and I'm hoping to get Sergei's LDAP change pushed this weekend (although I might to step up and finish the documentation side off!). Is this enough for a major bump as I probably need to quote version

RE: patch release tomorrow

2016-08-06 Thread Steve Holme
On Tue, 2 Aug 2016, Daniel Stenberg wrote: > It is quite possible that the next release following 7.50.1 also will become > a > patch release since we don't have any particular changes queued up (that would I've already push Bill's mbedTLS NTLM addition and I'm hoping to get Sergei's LDAP

Re: patch release tomorrow

2016-08-02 Thread Daniel Stenberg
On Tue, 2 Aug 2016, Richard Gray wrote: Possibly most notable: we're reverting the change that modified the CURL, CURLM and CURLSH types and they go back to be 'void *' unless you define CURL_STRICTER before including our headers. I wonder if there's an itch that wants to be scratched in

Re: patch release tomorrow

2016-08-02 Thread Daniel Stenberg
On Tue, 2 Aug 2016, Ray Satiro via curl-library wrote: I don't think that is the lesson here. I recall it has happened more than once that a file needed by a release is missing. The lesson I think would be to build from the planned release tarball prior to the actual release to make sure it

Re: patch release tomorrow

2016-08-02 Thread Richard Gray
dev_user wrote: On 08/02/2016 05:18 AM, Daniel Stenberg wrote: Hi all! I'll put together a 7.50.1 patch release tomorrow. ... Possibly most notable: we're reverting the change that modified the CURL, CURLM and CURLSH types and they go back to be 'void *' unless > you define CURL_STRIC

Re: patch release tomorrow

2016-08-02 Thread Ray Satiro via curl-library
On 8/2/2016 9:34 AM, Daniel Stenberg wrote: 7.50.0 :TESTFAIL: These test cases failed: 1139 1140 So hopefully 7.50.1 reports a 100% clear on the testsuite. We run most of our autobuild tests directly from git, so for example these two tests 1139 and 1140 will succeed off git but fail in a

Re: patch release tomorrow

2016-08-02 Thread Daniel Stenberg
On Tue, 2 Aug 2016, dev_user wrote: Excellent. I will watch for that. As I noted on my email 27th July 2016 there seems to be a few tests that fail in various versions released over the past little while : 7.50.0 :TESTFAIL: These test cases failed: 1139 1140 So hopefully 7.50.1 reports a

Re: patch release tomorrow

2016-08-02 Thread dev_user
On 08/02/2016 05:18 AM, Daniel Stenberg wrote: Hi all! I'll put together a 7.50.1 patch release tomorrow. Excellent. I will watch for that. As I noted on my email 27th July 2016 there seems to be a few tests that fail in various versions released over the past little while : 7.47.0

patch release tomorrow

2016-08-02 Thread Daniel Stenberg
Hi all! I'll put together a 7.50.1 patch release tomorrow. It'll include fixes for three minor security problems and the set of bugfixes we've landed so far since 7.50.0. Possibly most notable: we're reverting the change that modified the CURL, CURLM and CURLSH types and they go back