Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 19120 invoked from network); 3 Dec 2001 21:38:11 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Dec 2001 21:38:11 -0000 Received: (qmail 14188 invoked by uid 97); 3 Dec 2001 21:38:08 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 14171 invoked by uid 97); 3 Dec 2001 21:38:07 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 14160 invoked from network); 3 Dec 2001 21:38:07 -0000 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.1 Date: Mon, 03 Dec 2001 14:38:39 -0700 From: "Mike Anderson" To: Subject: RE: JK versions Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >>> costinm@covalent.net 12/03/01 01:53PM >>> On Mon, 3 Dec 2001 costinm@covalent.net wrote: >> On Mon, 3 Dec 2001, GOMEZ Henri wrote: >> >> > Ok, let's release mod_jk to 1.2 and start 2.0. >> >> For 1.2 we have 2 choices: >> - Branch it at Nov 15 ( or around ), i.e. before jk_channel and the new >> stuff ( that will be part of jk2.0 ) was added. > >After reading the commit log - most changes related to jk_channel, >jk_registry, etc are pretty safe ( as they don't change any logic ). > >We could actually release Jk1.2 using the main tree - if everyone is >comfortable with that. If not - Oct21 is probably a good point to branch >( the release date for 3.3 ). I'm afraid that we need to go back to an earlier date and re-port some fixes. The main reason is because the default 3.3 workers.properties still reference ajp12 which the current codebase no longer supports. This causes the plugins to fail during initialization since the ajp12_worker_factory isn't even in the main tree. Either that, or we add ajp12 support back in long enough to do a release. I'll be happy to help either way. >There are few fixes for ebcdic support and few small things that would >have to be re-applied. > >Costin Mike Anderson -- To unsubscribe, e-mail: For additional commands, e-mail: