On Tue, Feb 21, 2012 at 11:11 PM, Mladen Turk <mt...@apache.org> wrote:
> On 02/22/2012 06:17 AM, Costin Manolache wrote: > >> Mladen: please let me know if you want to further review the change or >> should I merge it to the branch. >> >> > Well I personally would not merge that into 1.1.x branch. > It would be a bit weird to have 1.1.22 as is, and 1.1.23 with > whole bunch of new features and API's. > That's not why we introduced branches at the first place. > > That's right, I agree. > > I also noticed there are few other diffs - in particular the 'interrupt' >> stuff in poll, few others. >> Any plans to merge them too ? >> > > Nope. Not to the 1.1.x branch > > > What's the plan with the trunk ? >> >> > We can release 1.2.0 from trunk. > That was my question - I didn't see any releases out of trunk, I assumed it's used for development and after some 'soak' merged back into 1.1.x > I see no problem with that. > It requires apr-1.4.x so this might be a solution for > that sslext code instead porting that back to 1.1.x > sslext works best with openssl 1.0.1 beta 2 ( i.e. latest ) - to get npn working with older ssl it needs a patch ( nodejs, chrome do this ). But it compiles and just lacks the npn feature without the patch. So for me a 1.2.x with recent apr and openssl would be best. > We can require 1.2.x for tomcat8 and actually use that > new API's without worrying on backward compatibility. I'm also interested in using the jni code 'standalone', so a native release without tomcat8 would also be nice. But no hurry - I was confused on the trunk->release branch policy. The main problem with jni is getting it compiled and installed on users machines. Costin > > > > > Regards > -- > ^TM > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@tomcat.apache.**org<dev-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
