Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 784 invoked from network); 8 Aug 2007 21:03:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Aug 2007 21:03:06 -0000 Received: (qmail 62184 invoked by uid 500); 8 Aug 2007 21:03:01 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 62103 invoked by uid 500); 8 Aug 2007 21:03:01 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 62092 invoked by uid 99); 8 Aug 2007 21:03:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 14:03:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.22.94.67] (HELO virtual.halosg.com) (72.22.94.67) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 21:02:54 +0000 Received: (qmail 15816 invoked from network); 8 Aug 2007 15:56:18 -0500 Received: from 72-19-171-38.static.mesanetworks.net (HELO ?192.168.3.103?) (72.19.171.38) by halosg.com with SMTP; 8 Aug 2007 15:56:18 -0500 Message-ID: <46BA2F60.5060306@hanik.com> Date: Wed, 08 Aug 2007 15:02:24 -0600 From: Filip Hanik - Dev Lists User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Tomcat Developers List Subject: status of trunk Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org what is the plan for trunk? the reason I started the 6.x feature list was to get some development going for the next version of Tomcat. Remy was the one who initiated trunk and suggested future development to go in there. Is there anything but the disagreement around the CometEvent interface holding this back? There are already several enhancements in trunk that are not in 6.0, not comet related, but if we are not moving trunk forward, then its time to merge the branches back to 6.0.x personally I would prefer 1. resolve the issue around the CometEvent interface, (it was resolved when Remy pulled back his proposal, but from what I understand, its coming back) 2. continue future development in trunk thoughts... Filip --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org