You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Leif Hedstrom <zw...@apache.org> on 2015/01/02 18:15:40 UTC
Re: [VOTE] Release v5.2.0
> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> Hi all,
>
> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>
> * TLS dynamic record sizing
> * Add forward secrecy support with DHE
> * Backtrace support via traffic_line command line
> * Improved crash logging
> * Background fetch plugin has been improved with new features
I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
*) [TS-3083] Fix core dump due to FetchSM double delete.
*) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
*) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
*) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
-rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
-rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
-rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
-rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
MD5: 4040edb2032f1a860c831c581a5f968c
SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
Thanks!
— Leif
Re: [VOTE] Release v5.2.0
Posted by "Neddy, NH. Nam" <na...@nd24.net>.
Leif, it's the same build from RC0 to RC2, and I'm running RC2 as well.
On Mon, Jan 5, 2015 at 11:42 AM, Leif Hedstrom <zw...@apache.org> wrote:
> Any details ? None of our CI build boxes are failing. Did RC2 work?
>
> -- Leif
>
>
>
>> On Jan 4, 2015, at 6:44 PM, Neddy, NH. Nam <na...@nd24.net> wrote:
>>
>> I can't build RC3 on Debian Whezzy x64.
>>
>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>> --with-ncurses --with-openssl=/usr
>>
>>> On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>>>
>>>> * TLS dynamic record sizing
>>>> * Add forward secrecy support with DHE
>>>> * Backtrace support via traffic_line command line
>>>> * Improved crash logging
>>>> * Background fetch plugin has been improved with new features
>>>
>>>
>>> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>>>
>>>
>>> *) [TS-3083] Fix core dump due to FetchSM double delete.
>>>
>>> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>>>
>>> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>>>
>>> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>>>
>>>
>>>
>>> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>>>
>>> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
>>> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
>>> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
>>> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>>>
>>>
>>> MD5: 4040edb2032f1a860c831c581a5f968c
>>> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>>>
>>>
>>> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>>>
>>> Thanks!
>>>
>>> — Leif
>> <ts520rc3-20150105.txt>
Re: [VOTE] Release v5.2.0
Posted by "Neddy, NH. Nam" <na...@nd24.net>.
Leif, it's the same build from RC0 to RC2, and I'm running RC2 as well.
On Mon, Jan 5, 2015 at 11:42 AM, Leif Hedstrom <zw...@apache.org> wrote:
> Any details ? None of our CI build boxes are failing. Did RC2 work?
>
> -- Leif
>
>
>
>> On Jan 4, 2015, at 6:44 PM, Neddy, NH. Nam <na...@nd24.net> wrote:
>>
>> I can't build RC3 on Debian Whezzy x64.
>>
>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>> --with-ncurses --with-openssl=/usr
>>
>>> On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>>>
>>>> * TLS dynamic record sizing
>>>> * Add forward secrecy support with DHE
>>>> * Backtrace support via traffic_line command line
>>>> * Improved crash logging
>>>> * Background fetch plugin has been improved with new features
>>>
>>>
>>> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>>>
>>>
>>> *) [TS-3083] Fix core dump due to FetchSM double delete.
>>>
>>> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>>>
>>> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>>>
>>> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>>>
>>>
>>>
>>> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>>>
>>> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
>>> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
>>> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
>>> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>>>
>>>
>>> MD5: 4040edb2032f1a860c831c581a5f968c
>>> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>>>
>>>
>>> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>>>
>>> Thanks!
>>>
>>> — Leif
>> <ts520rc3-20150105.txt>
Re: [VOTE] Release v5.2.0
Posted by Mohd Akhbar <my...@gmail.com>.
+1 on Centos 6.5 on XenServer's VM
On Mon, Jan 5, 2015 at 12:42 PM, Leif Hedstrom <zw...@apache.org> wrote:
> Any details ? None of our CI build boxes are failing. Did RC2 work?
>
> -- Leif
>
>
>
>> On Jan 4, 2015, at 6:44 PM, Neddy, NH. Nam <na...@nd24.net> wrote:
>>
>> I can't build RC3 on Debian Whezzy x64.
>>
>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>> --with-ncurses --with-openssl=/usr
>>
>>> On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>>>
>>>> * TLS dynamic record sizing
>>>> * Add forward secrecy support with DHE
>>>> * Backtrace support via traffic_line command line
>>>> * Improved crash logging
>>>> * Background fetch plugin has been improved with new features
>>>
>>>
>>> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>>>
>>>
>>> *) [TS-3083] Fix core dump due to FetchSM double delete.
>>>
>>> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>>>
>>> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>>>
>>> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>>>
>>>
>>>
>>> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>>>
>>> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
>>> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
>>> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
>>> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>>>
>>>
>>> MD5: 4040edb2032f1a860c831c581a5f968c
>>> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>>>
>>>
>>> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>>>
>>> Thanks!
>>>
>>> — Leif
>> <ts520rc3-20150105.txt>
Re: [VOTE] Release v5.2.0
Posted by Leif Hedstrom <zw...@apache.org>.
Any details ? None of our CI build boxes are failing. Did RC2 work?
-- Leif
> On Jan 4, 2015, at 6:44 PM, Neddy, NH. Nam <na...@nd24.net> wrote:
>
> I can't build RC3 on Debian Whezzy x64.
>
> ./configure --prefix=/opt/ats520 --enable-static-proxy
> --enable-experimental-plugins --enable-test-tools --with-user=proxy
> --with-ncurses --with-openssl=/usr
>
>> On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>>
>>> * TLS dynamic record sizing
>>> * Add forward secrecy support with DHE
>>> * Backtrace support via traffic_line command line
>>> * Improved crash logging
>>> * Background fetch plugin has been improved with new features
>>
>>
>> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>>
>>
>> *) [TS-3083] Fix core dump due to FetchSM double delete.
>>
>> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>>
>> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>>
>> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>>
>>
>>
>> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>>
>> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
>> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
>> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
>> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>>
>>
>> MD5: 4040edb2032f1a860c831c581a5f968c
>> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>>
>>
>> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>>
>> Thanks!
>>
>> — Leif
> <ts520rc3-20150105.txt>
Re: [VOTE] Release v5.2.0
Posted by Leif Hedstrom <zw...@apache.org>.
Any details ? None of our CI build boxes are failing. Did RC2 work?
-- Leif
> On Jan 4, 2015, at 6:44 PM, Neddy, NH. Nam <na...@nd24.net> wrote:
>
> I can't build RC3 on Debian Whezzy x64.
>
> ./configure --prefix=/opt/ats520 --enable-static-proxy
> --enable-experimental-plugins --enable-test-tools --with-user=proxy
> --with-ncurses --with-openssl=/usr
>
>> On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>>
>>> * TLS dynamic record sizing
>>> * Add forward secrecy support with DHE
>>> * Backtrace support via traffic_line command line
>>> * Improved crash logging
>>> * Background fetch plugin has been improved with new features
>>
>>
>> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>>
>>
>> *) [TS-3083] Fix core dump due to FetchSM double delete.
>>
>> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>>
>> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>>
>> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>>
>>
>>
>> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>>
>> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
>> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
>> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
>> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>>
>>
>> MD5: 4040edb2032f1a860c831c581a5f968c
>> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>>
>>
>> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>>
>> Thanks!
>>
>> — Leif
> <ts520rc3-20150105.txt>
Re: [VOTE] Release v5.2.0
Posted by James Peach <jp...@apache.org>.
> On Jan 5, 2015, at 10:20 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>>
>> On Jan 5, 2015, at 11:17 AM, James Peach <jp...@apache.org> wrote:
>>
>>
>>> On Jan 5, 2015, at 4:05 AM, Nick Kew <ni...@apache.org> wrote:
>>>
>>> On Mon, 2015-01-05 at 08:44 +0700, Neddy, NH. Nam wrote:
>>>> I can't build RC3 on Debian Whezzy x64.
>>>>
>>>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>>>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>>>> --with-ncurses --with-openssl=/usr
>>>
>>> I can reproduce exactly that on wheezy. The culprit is the
>>> --enable-static-proxy, without which it builds just fine.
>>> What's the history of that option? I've never used it,
>>> and it appears not to exist in 4.x.
>>
>> Apparantly in the past, people built the traffic_server binary static for performance reasons (the --enable-static-libts build option). I introduced this build option to preserve the original use case, but to play better with automake linking options. I'll try to fix this …
>
>
> Cool, thanks James. Please file a Jira for this unless there already is one. I’m not going to stop the release process for v5.2.0 for this, but we can consider a backport for v5.2.1 if there is a need / wish for it.
>
> Fwiw, the performance reasons, afaik, was for 32-bit platforms, where the static linking could save a register. I don’t know that we care much for that any more, right?
I'm happy to nuke it or to commit a patch that nukes it
J
Re: [VOTE] Release v5.2.0
Posted by Leif Hedstrom <zw...@apache.org>.
> On Jan 5, 2015, at 11:17 AM, James Peach <jp...@apache.org> wrote:
>
>
>> On Jan 5, 2015, at 4:05 AM, Nick Kew <ni...@apache.org> wrote:
>>
>> On Mon, 2015-01-05 at 08:44 +0700, Neddy, NH. Nam wrote:
>>> I can't build RC3 on Debian Whezzy x64.
>>>
>>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>>> --with-ncurses --with-openssl=/usr
>>
>> I can reproduce exactly that on wheezy. The culprit is the
>> --enable-static-proxy, without which it builds just fine.
>> What's the history of that option? I've never used it,
>> and it appears not to exist in 4.x.
>
> Apparantly in the past, people built the traffic_server binary static for performance reasons (the --enable-static-libts build option). I introduced this build option to preserve the original use case, but to play better with automake linking options. I'll try to fix this …
Cool, thanks James. Please file a Jira for this unless there already is one. I’m not going to stop the release process for v5.2.0 for this, but we can consider a backport for v5.2.1 if there is a need / wish for it.
Fwiw, the performance reasons, afaik, was for 32-bit platforms, where the static linking could save a register. I don’t know that we care much for that any more, right?
Cheers,
— leif
Re: [VOTE] Release v5.2.0
Posted by James Peach <jp...@apache.org>.
> On Jan 5, 2015, at 4:05 AM, Nick Kew <ni...@apache.org> wrote:
>
> On Mon, 2015-01-05 at 08:44 +0700, Neddy, NH. Nam wrote:
>> I can't build RC3 on Debian Whezzy x64.
>>
>> ./configure --prefix=/opt/ats520 --enable-static-proxy
>> --enable-experimental-plugins --enable-test-tools --with-user=proxy
>> --with-ncurses --with-openssl=/usr
>
> I can reproduce exactly that on wheezy. The culprit is the
> --enable-static-proxy, without which it builds just fine.
> What's the history of that option? I've never used it,
> and it appears not to exist in 4.x.
Apparantly in the past, people built the traffic_server binary static for performance reasons (the --enable-static-libts build option). I introduced this build option to preserve the original use case, but to play better with automake linking options. I'll try to fix this ...
J
Re: [VOTE] Release v5.2.0
Posted by Nick Kew <ni...@apache.org>.
On Mon, 2015-01-05 at 08:44 +0700, Neddy, NH. Nam wrote:
> I can't build RC3 on Debian Whezzy x64.
>
> ./configure --prefix=/opt/ats520 --enable-static-proxy
> --enable-experimental-plugins --enable-test-tools --with-user=proxy
> --with-ncurses --with-openssl=/usr
I can reproduce exactly that on wheezy. The culprit is the
--enable-static-proxy, without which it builds just fine.
What's the history of that option? I've never used it,
and it appears not to exist in 4.x.
--
Nick Kew
Re: [VOTE] Release v5.2.0
Posted by "Neddy, NH. Nam" <na...@nd24.net>.
I can't build RC3 on Debian Whezzy x64.
./configure --prefix=/opt/ats520 --enable-static-proxy
--enable-experimental-plugins --enable-test-tools --with-user=proxy
--with-ncurses --with-openssl=/usr
On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>> Hi all,
>>
>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>
>> * TLS dynamic record sizing
>> * Add forward secrecy support with DHE
>> * Backtrace support via traffic_line command line
>> * Improved crash logging
>> * Background fetch plugin has been improved with new features
>
>
> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>
>
> *) [TS-3083] Fix core dump due to FetchSM double delete.
>
> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>
> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>
> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>
>
>
> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>
> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>
>
> MD5: 4040edb2032f1a860c831c581a5f968c
> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>
>
> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>
> Thanks!
>
> — Leif
>
Re: [VOTE] Release v5.2.0
Posted by "Neddy, NH. Nam" <na...@nd24.net>.
I can't build RC3 on Debian Whezzy x64.
./configure --prefix=/opt/ats520 --enable-static-proxy
--enable-experimental-plugins --enable-test-tools --with-user=proxy
--with-ncurses --with-openssl=/usr
On Sat, Jan 3, 2015 at 12:15 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On Dec 16, 2014, at 3:52 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>> Hi all,
>>
>> I've prepared a release candidate for v5.2.0, which is primarily a bug fix release over v5.1.x, but also adds a few noteworthy features:
>>
>> * TLS dynamic record sizing
>> * Add forward secrecy support with DHE
>> * Backtrace support via traffic_line command line
>> * Improved crash logging
>> * Background fetch plugin has been improved with new features
>
>
> I’ve finally prepared an RC3 candidate, which fixes the following issues (from RC2):
>
>
> *) [TS-3083] Fix core dump due to FetchSM double delete.
>
> *) [TS-3262] Change abs() to std::abs(), avoid compiler errors.
>
> *) [TS-3265] Fix spdy req_map access to use iterator instead of operator[].
>
> *) [TS-3261] Fix SSL BIO memory leak issue introduced in TS-3006.
>
>
>
> The new candidate is available on the same place, http://people.apache.org/~zwoop/rel-candidates/:
>
> -rw-r--r-- 1 zwoop zwoop 7664971 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2
> -rw-r--r-- 1 zwoop zwoop 949 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Jan 2 16:54 trafficserver-5.2.0-rc3.tar.bz2.sha1
>
>
> MD5: 4040edb2032f1a860c831c581a5f968c
> SHA1: a1bea69f63eae9e350cb91a1e0035bcd340cf722
>
>
> The vote is open until January 7th. Keep up the good work, test this bad boy and cast your votes (or file Jira’s).
>
> Thanks!
>
> — Leif
>