From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id BB122BC6B for ; Fri, 27 Apr 2007 11:15:45 +0200 (CEST) Received: from [128.93.11.95] (estephe.inria.fr [128.93.11.95]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l3R9FV1f027931; Fri, 27 Apr 2007 11:15:31 +0200 Message-ID: <4631BF33.6080407@inria.fr> Date: Fri, 27 Apr 2007 11:15:31 +0200 From: Xavier Leroy User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: Markus Mottl Cc: Martin Jambon , Diego Olivier FERNANDEZ PONS , caml-list@inria.fr, skaller Subject: Re: new+old Camlp4 References: <001401c785f3$3af5e890$6a7ba8c0@treble> <1177392571.10100.46.camel@rosella.wigram> <20070424122338.ozkvhzfhckcskkc4@webmail.etu.upmc.fr> <1177439118.6172.18.camel@rosella.wigram> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 4631BF33.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; camlp:01 camlp:01 bug-fix:01 minor:01 rewrite:01 delayed:01 macros:01 macros:01 generally:03 i'd:05 xavier:06 xavier:06 inria:06 inria:06 usual:06 > I'd therefore strongly suggest that INRIA plan more carefully how to > make the next release. From my point of view, the best way would be > to provide sufficient documentation in advance to allow Camlp4 > developers to rewrite their macros in time. I agree with the need for documentation, but not with the timing you propose. Release 3.10.0 has been delayed quite a bit already, and 1- there is no reason to make users who do not depend on Camlp4 wait longer for 3.10; 2- having the new Camlp4 officially released as part of 3.10.0 can only facilitate the porting of Camlp4 macros and extensions. More generally, we are painfully aware that the transition from 3.09 to 3.10 is a minor upgrade for users who do not depend on Camlp4, but a major change for Camlp4 users. We plan to maintain 3.09 (by making bug-fix releases) longer than usual so that users who are stuck with the old Camlp4 can stay with 3.09 for a while. Nobody is forced to upgrade to 3.10 immediately. Releasing both old and new Camlp4 as part of 3.10 is out of the question, however. That would only delay the inevitable and would waste a lot of our time to make such a release. The priorities are 1- get 3.10.0 out of the door, and 2- of course, provide more documentation on the new Camlp4. - Xavier Leroy