Hi,
Apache Tomcat Connectors 1.2.38 release candidate is ready
for vote at [1]. This version fixes few bugs found in released
version 1.2.37 and adds some new features like IPV6 support.
The VOTE will remain open for at least 48 hours.
The Apache Tomcat Connectors 1.2.38 is
[ ] Stable, go
On 02/26/2014 09:45 AM, Mladen Turk wrote:
Hi,
Apache Tomcat Connectors 1.2.38 release candidate is ready
for vote at [1]. This version fixes few bugs found in released
version 1.2.37 and adds some new features like IPV6 support.
The VOTE will remain open for at least 48 hours.
The Apache
On 02/26/2014 09:55 AM, jean-frederic clere wrote:
On 02/26/2014 09:45 AM, Mladen Turk wrote:
+++
/home/jfclere/APACHE-2.2.21/build/libtool --silent --mode=compile gcc
-I/home/jfclere/APACHE-2.2.21/include -DHAVE_CONFIG_H -ansi -pedantic
-Wno-long-long -Wall -pthread -DHAVE_APR
On 26.02.2014 09:45, Mladen Turk wrote:
Hi,
Apache Tomcat Connectors 1.2.38 release candidate is ready
for vote at [1]. This version fixes few bugs found in released
version 1.2.37 and adds some new features like IPV6 support.
The VOTE will remain open for at least 48 hours.
The
On 02/26/2014 11:18 AM, Rainer Jung wrote:
No other finding currently, but still checking some stuff. Just wanted
to let you know quickly.
OK. Give it a try. I'll just retag 1.2.39 with all the polishing stuff
found. It's been a while since last release, so I was prepared for few runs :)
On 26.02.2014 11:48, Mladen Turk wrote:
On 02/26/2014 11:18 AM, Rainer Jung wrote:
No other finding currently, but still checking some stuff. Just wanted
to let you know quickly.
OK. Give it a try. I'll just retag 1.2.39 with all the polishing stuff
found. It's been a while since last
On 02/26/2014 02:30 PM, Rainer Jung wrote:
On 26.02.2014 11:48, Mladen Turk wrote:
native/nt_service/jk_nt_service.c still uses jk_resolve() with
sockaddr_in instead of tne new jk struct. Should we remove
native/nt_service or apply the probably simple fix to make it compatible
with the new jk
Due to some issues found this vote is canceled
Should I retag 1.2.38 or create 1.2.39?
If later can we use the
section name=Changes between 1.2.37 and 1.2.39
in the changelog since 1.2.38 was not released?
On 02/26/2014 09:45 AM, Mladen Turk wrote:
Hi,
Apache Tomcat Connectors 1.2.38
On 26.02.2014 17:19, Mladen Turk wrote:
Due to some issues found this vote is canceled
Should I retag 1.2.38 or create 1.2.39?
I'd slightly prefer we switch to 1.2.39 to ensure noone is using the
obsolete 1.2.38 instead of the released code.
If later can we use the
section name=Changes
On 02/26/2014 06:10 PM, Rainer Jung wrote:
On 26.02.2014 17:19, Mladen Turk wrote:
Due to some issues found this vote is canceled
Should I retag 1.2.38 or create 1.2.39?
I'd slightly prefer we switch to 1.2.39 to ensure noone is using the
obsolete 1.2.38 instead of the released code.
If
10 matches
Mail list logo
