Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 37219 invoked from network); 17 Nov 2010 00:10:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Nov 2010 00:10:40 -0000 Received: (qmail 30297 invoked by uid 500); 17 Nov 2010 00:11:10 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 30160 invoked by uid 500); 17 Nov 2010 00:11:10 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 30147 invoked by uid 99); 17 Nov 2010 00:11:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Nov 2010 00:11:10 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [193.74.71.28] (HELO sif.is.scarlet.be) (193.74.71.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Nov 2010 00:11:02 +0000 Received: from mail.harfang.homelinux.org (ip-213-49-251-6.dsl.scarlet.be [213.49.251.6]) by sif.is.scarlet.be (8.14.2/8.14.2) with ESMTP id oAH0AfZY029540 for ; Wed, 17 Nov 2010 01:10:41 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scarlet.be; s=scarlet; t=1289952641; bh=W2LI/BMbbLmNIvxAUYw+vxIMKzIyS+3relWa5xy8QV4=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=YanpK1sD47TQ7dbA3vzRZcGtL8AYUHEwoEA5xUicMB5DtCH8P/lOt694JvPgC2o6n gYTn31+GQP1vqcvfys4mxcRIETK2RjS+m5CAXPhmGAaOUcP+SWwbPKMQ3fccY5TZ4b 7wIvnVGTRCZho8qYdlbvCKPRVMgySQyfO81wUbRo= Received: from localhost (mail.harfang.homelinux.org [192.168.20.11]) by mail.harfang.homelinux.org (Postfix) with ESMTP id 06D98617F2 for ; Wed, 17 Nov 2010 01:10:41 +0100 (CET) Received: from mail.harfang.homelinux.org ([192.168.20.11]) by localhost (mail.harfang.homelinux.org [192.168.20.11]) (amavisd-new, port 10024) with ESMTP id uvJoUl0qnR7P for ; Wed, 17 Nov 2010 01:10:38 +0100 (CET) Received: from dusk.harfang.homelinux.org (mail.harfang.homelinux.org [192.168.20.11]) by mail.harfang.homelinux.org (Postfix) with ESMTP id B80AB617EE for ; Wed, 17 Nov 2010 01:10:38 +0100 (CET) Received: from eran by dusk.harfang.homelinux.org with local (Exim 4.72) (envelope-from ) id 1PIVbi-0001gK-D7 for dev@commons.apache.org; Wed, 17 Nov 2010 01:10:38 +0100 Date: Wed, 17 Nov 2010 01:10:36 +0100 From: Gilles Sadowski To: dev@commons.apache.org Subject: Re: [math] preparing smooth interface upgrade for users Message-ID: <20101117001036.GM10411@dusk.harfang.homelinux.org> Mail-Followup-To: dev@commons.apache.org References: <4CE2EEF4.2030204@free.fr> <20101116231944.GL10411@dusk.harfang.homelinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Tiny Tux X-PGP-Key-Fingerprint: 53B9 972E C2E6 B93C BEAD 7092 09E6 AF46 51D0 5641 User-Agent: Mutt/1.5.20 (2009-06-14) X-DCC-scarlet.be-Metrics: sif 20001; Body=1 Fuz1=1 Fuz2=1 X-Virus-Checked: Checked by ClamAV on apache.org > >> [...] > >> I think this transition is the smoother path for our users. Do you think > >> this change is the way to go ? > > > > -0 > > +1 > > > > > My first impression is that it is a lot of changes for 2.2 without any > > benefit when users will switch to 3.0; they will still have to scan their > > code for all the exceptions that will have disappeared. > > Won't the deprecations take care of that? I didn't mean that they have to scan "manually", just that they will have to make the same change in 3.0 as they would in 2.2 (not more, not less work). Hence, I see no benefit in breaking the "no compatibility breaking" rule in 2.2. > > > In 3.0 it will clear that they *have* to do it while, in 2.2, you would > > have to explain to users that it's better that they do it but that it > > will still work if they don't... And they will probably say: "If it ain't > > broken, I won't fix it." ;-) > > However, deprecation warnings are a strong hint that failure is > imminent, and they may wish to prepare for the change. Yes. We should advertise the list of exceptions that are going to be replaced by "MathUserException" when users switch 3.0, by deprecating them in 2.2. The preparation is to have a perl (or sed or ...) script ready. Best, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org