Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
MIME-Version: 1.0
In-Reply-To: <56617C24.8040802@apache.org>
References: <56617C24.8040802@apache.org>
Date: Fri, 4 Dec 2015 13:38:32 +0100
Message-ID: 
 <CANwj8Zr-CUPwPfd+5hZMSxDEPc9iNj7KvaKhb56qvqp3idmybA@mail.gmail.com>
Subject: Re: Time for tomcat-native 1.2.3?
From: =?UTF-8?Q?R=C3=A9my_Maucherat?= <remm@apache.org>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a113deba00e11ab052611c9a5

--001a113deba00e11ab052611c9a5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2015-12-04 12:42 GMT+01:00 Mark Thomas <markt@apache.org>:

> Give the recent OpenSSL vulnerability announcements [1], I was planning
> on starting a tomcat-native 1.2.3 release to provide an updated Windows
> binary.
>
> There are a few fixes in trunk since 1.2.2. I'll get the changelog update=
d.
>

Sorry, I guess everyone forgot there's a changelog there as well.

>
> I'm currently planning on tagging this on Tuesday 8th Dec. We can
> probably afford to wait a couple of days if anyone wants to get anything
> else into a 1.2.3 release.
>
> On a related topic, what are people's views on switching 6.0.x, 7.0.x
> and 8.0.x to 1.2.x rather than 1.1.x?
>
> I am investigating an issue where SSL.getPeerCertificate always returns
null (for whatever reason), which may need some fixes, so it's not certain
renegotiation works at the moment (although it looks like it). Hopefully
this will be sorted out to be included in the tag.

About forcing an update to 1.2.x for all branches, I'm not convinced at the
moment.

R=C3=A9my

--001a113deba00e11ab052611c9a5--