caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: Martin Jambon <martin.jambon@ens-lyon.org>,
	Diego Olivier FERNANDEZ PONS <diego.fernandez_pons@etu.upmc.fr>,
	caml-list@inria.fr, skaller <skaller@users.sourceforge.net>
Subject: Re: new+old Camlp4
Date: Fri, 27 Apr 2007 11:15:31 +0200	[thread overview]
Message-ID: <4631BF33.6080407@inria.fr> (raw)
In-Reply-To: <f8560b80704251011n6a24fc9aq69a6fff46427c143@mail.gmail.com>

> 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


  parent reply	other threads:[~2007-04-27  9:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 22:03 Bug in ocamlyacc David Allsopp
2007-04-24  5:29 ` [Caml-list] " skaller
2007-04-24 10:23   ` Diego Olivier FERNANDEZ PONS
2007-04-24 12:06     ` ls-ocaml-developer-2006
2007-04-24 18:25     ` skaller
2007-04-24 20:17       ` new+old Camlp4 (was Re: [Caml-list] Bug in ocamlyacc) Martin Jambon
2007-04-24 21:38         ` Yaron Minsky
2007-04-24 22:53           ` new+old Camlp4 ls-ocaml-developer-2006
2007-04-25  1:03         ` new+old Camlp4 (was Re: [Caml-list] Bug in ocamlyacc) skaller
2007-04-25  2:29         ` Daniel de Rauglaudre
2007-04-25 17:11         ` Markus Mottl
2007-04-26  3:00           ` skaller
2007-04-27  9:15           ` Xavier Leroy [this message]
2007-04-27 13:43             ` new+old Camlp4 Markus Mottl
2007-05-02  8:03             ` [Caml-list] " Hendrik Tews
2007-04-24 14:32   ` [Caml-list] Bug in ocamlyacc Francois Pottier
2007-04-24 18:59     ` skaller
2007-04-24 19:59       ` Francois Pottier
2007-04-27 15:56     ` brogoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4631BF33.6080407@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=diego.fernandez_pons@etu.upmc.fr \
    --cc=markus.mottl@gmail.com \
    --cc=martin.jambon@ens-lyon.org \
    --cc=skaller@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).