Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 6602 invoked from network); 9 May 2004 21:10:11 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 May 2004 21:10:11 -0000 Received: (qmail 83351 invoked by uid 500); 9 May 2004 21:09:55 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 82894 invoked by uid 500); 9 May 2004 21:09:52 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 82881 invoked from network); 9 May 2004 21:09:52 -0000 Received: from unknown (HELO warden.diginsite.com) (208.29.163.248) by daedalus.apache.org with SMTP; 9 May 2004 21:09:52 -0000 Received: from wlvims01.diginsite.com by warden.diginsite.com via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Sun, 9 May 2004 14:09:58 -0700 Received: by calexc01.diginsite.com with Internet Mail Service (5.5.2657.72) id ; Sun, 9 May 2004 14:08:48 -0700 Message-ID: <31DF72A980E5D511B48C000102BD8685061DB3D4@calexc01.diginsite.com> From: Ralph Goers To: "'dev@cocoon.apache.org'" Subject: [VOTE] RE: LogKitLoggerManager Date: Sun, 9 May 2004 14:08:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Yes, this change is backward compatible with 2.1.4, but not with the version Carsten checked in last week. I'd appreciate a vote to have this patch applied. Ralph -----Original Message----- From: Joerg Heinicke [mailto:joerg.heinicke@gmx.de] Sent: Sunday, May 09, 2004 1:52 PM To: dev@cocoon.apache.org Subject: Re: LogKitLoggerManager On 09.05.2004 19:25, Ralph Goers wrote: > I've submitted patch 28860. I realize this is after the code freeze, but I'd > prefer to see this patch instead of the current code. If 2.1.5 goes out with > the current code we would have to maintain the current behavior of > logger-type. I guess it's completely backwards compatible (same default behaviour and so on). Then it can go in, but we must vote about it. It's best if you start the vote yourself. But IMO we should not wait 72 h for that vote as we would have only Thursday to test it. 36 h are enough for this case IMO. Joerg