Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 20211 invoked from network); 3 May 2007 14:24:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 May 2007 14:24:52 -0000 Received: (qmail 43276 invoked by uid 500); 3 May 2007 14:24:58 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 43263 invoked by uid 500); 3 May 2007 14:24:58 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 43252 invoked by uid 99); 3 May 2007 14:24:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 07:24:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [203.202.1.123] (HELO barge.anchor.net.au) (203.202.1.123) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 07:24:50 -0700 Received: from [127.0.0.1] (dsl-58-6-32-215.nsw.westnet.com.au [58.6.32.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by barge.anchor.net.au (Postfix) with ESMTP id D8A9510102 for ; Fri, 4 May 2007 00:25:27 +1000 (EST) Message-ID: <4639F058.8010503@backstagetech.com.au> Date: Fri, 04 May 2007 00:23:20 +1000 From: Scott Eade User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Apache Torque Developers List Subject: Re: Torque 3.3-RC3 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thomas Fischer wrote: > It is not problematic to fix the doDelete()-Problem, this would take about > half an hour or so. I am still of the opinion that it should be fixed as > proposed, and could do it on Saturday. > You said that you would rather like to document the error than fixing it. > Do you strongly object the fix ? > > I have no opinion at all about the texen stuff. As you said, it makes no > sense to use texen separately if we still use velocity 1.3. Do you think we > should upgrade to 1.5 ? I recall dimly that some people reported problems > with velocity 1.4, but I can not recall any details. Are we reasonably > confident that these problems do not exist in velocity 1.5 any more ? > I think there was some mention of a memory leak somewhere in 1.4 that was apparent in the way it was used by torque. I am pretty sure this will have been addressed in velocity 1.5 - Thomas V. can check this with Henning IRL. I'd like to see us on 1.5 for the sake of consistency. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org