Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 2725 invoked from network); 7 Sep 2003 14:15:00 -0000 Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by daedalus.apache.org with SMTP; 7 Sep 2003 14:15:00 -0000 Received: (qmail 35774 invoked from network); 7 Sep 2003 14:14:48 -0000 Received: from unknown (HELO apache.org) (127.0.0.1) by localhost with SMTP; 7 Sep 2003 14:14:48 -0000 Message-ID: <3F5B3D52.1090702@apache.org> Date: Sun, 07 Sep 2003 16:14:42 +0200 From: Remy Maucherat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: [5.0] Planning References: <20030906174931.49960.qmail@minotaur.apache.org> <3F5ACB07.3050207@apache.org> In-Reply-To: <3F5ACB07.3050207@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Rather than having a vote for 5.0.10, I'd like to release a new 5.0.11 build with the fix for the (nasty) commons-logging classloading issues. The idea is that using Struts 1.1 with log4j is quite common, and using that in conjunction with a context config file cut & pasted from the manager or admin (with the privileged="true" thingie) would produce a horrible stack trace. So I'd like to have it fixed in a release ASAP :) So the plan is: - have a new 5.0.11 beta this week (or a bit later if there are other issues that need fixing in that build) - have a "final" beta when the specs are released - have a stable release shortly after Comments ? Remy