On 08/12/2015 18:55, Konstantin Kolinko wrote: > 2015-12-04 14:42 GMT+03:00 Mark Thomas <ma...@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 updated. >> >> 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. > > +1. > >> 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 +1. > How about the following: > > Build both 1.1.34 and 1.2.3 now, but include 1.2.3 with future > releases of Tomcat 6/7/8. > > There a number of items in changelog for 1.1.34 release, so having one > would be nice, > as the final release in 1.1.x branch, > and as a backup option if 1.2.3 happens to be not as stable as we expect. > > I expect that 1.1.34 will go without Itanium binaries, as (as far as I > understand correctly) you cannot build those. I am OK with it.
That plan works for me. I might be able to build the Itanium binaries for 1.1.x. It depends which version of OpenSSL I build with. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
