Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 53916 invoked from network); 28 Jan 2004 16:20:00 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 28 Jan 2004 16:20:00 -0000 Received: (qmail 97838 invoked by uid 500); 28 Jan 2004 16:10:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 97772 invoked by uid 500); 28 Jan 2004 16:10:50 -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 97719 invoked from network); 28 Jan 2004 16:10:49 -0000 Received: from unknown (HELO warden.diginsite.com) (208.29.163.248) by daedalus.apache.org with SMTP; 28 Jan 2004 16:10:49 -0000 Received: from wlvims01.diginsite.com by warden.diginsite.com via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Wed, 28 Jan 2004 08:10:42 -0800 Received: from WLVIMS01 ([127.0.0.1]) by WLVIMS01.digitalinsight.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id com for ; Wed, 28 Jan 2004 08:10:30 -0800 Received: by calexc01.diginsite.com with Internet Mail Service (5.5.2657.72) id ; Wed, 28 Jan 2004 08:09:58 -0800 Message-ID: <31DF72A980E5D511B48C000102BD868503EA81B9@calexc01.diginsite.com> From: Ralph Goers To: "'dev@cocoon.apache.org'" Subject: RE: [proposal] Cleaning up our component library Date: Wed, 28 Jan 2004 08:09:57 -0800 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 I totally agree with this. I have focused totally on 2.1 in building our system. For things to suddenly be deprecated now would be most irritating. If 2.2 manages to make the process of building one's webapp easier with "real" blocks, a lot of folks like me will want to switch to it just for that. I really don't want to have to reimplement a bunch of stuff. -----Original Message----- From: Geoff Howard [mailto:cocoon@leverageweb.com] Sent: Wednesday, January 28, 2004 7:45 AM To: dev@cocoon.apache.org Subject: Re: [proposal] Cleaning up our component library What about doing "weak" deprecation, with good explanation that the move is in name only. INFO level logging on each use seems reasonable. But I'd propose that since this would come late in the 2.1 cycle that removing in 2.2 is too soon. I'd propose continue deprecation in 2.2 and remove only after that - maybe even a major version (i.e., 3.0). Geoff