caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <damien.doligez@inria.fr>
To: Jonas Jensen <jj@issuu.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml release roadmap
Date: Thu, 14 May 2015 16:51:24 -0400	[thread overview]
Message-ID: <CALGm1VhGaJUC8a0Hkuvcv3627_z7LgLhJ+BDXNU3nbYfncUwzw@mail.gmail.com> (raw)
In-Reply-To: <CAExvvWwSivFJc6==VSpD-U-dne=-4aBPw4tsAnS3azGfJ1o7HA@mail.gmail.com>

On Wed, May 13, 2015 at 9:20 AM, Jonas Jensen <jj@issuu.com> wrote:

> Is there a good reason not to release current trunk as 4.03 soon?

Manpower is one such reason. Also, we like to thoroughly test our
code before we release it. And there are several important features
in the works.

> According to http://caml.inria.fr/mantis/view.php?id=5528, the "Inline
> records for constructor arguments" feature has been merged to trunk. I
> think this is a huge improvement to the language that will improve
> code readability for at lot of projects.

I see it as a rather small feature. It's not in the same league as GADTs
or Modular Implicits, for example.

> An end-of-year release seems
> very far away, especially if the release date slips because multicore
> support is such a disruptive change.

I know our release schedule is rather slow, but OCaml is a really
complex system and we like to think things through before we
release, and this has already saved us from several bad design
decisions.

-- Damien

  reply	other threads:[~2015-05-14 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:24 Damien Doligez
2015-05-11 11:46 ` Francois Berenger
2015-05-11 13:31   ` Mark Shinwell
2015-05-11 13:31     ` Mark Shinwell
2015-05-26 17:13     ` Richard W.M. Jones
2015-06-04 20:34       ` Damien Doligez
2015-05-13 13:20 ` Jonas Jensen
2015-05-14 20:51   ` Damien Doligez [this message]
2015-05-14 21:20     ` Gabriel Scherer

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=CALGm1VhGaJUC8a0Hkuvcv3627_z7LgLhJ+BDXNU3nbYfncUwzw@mail.gmail.com \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=jj@issuu.com \
    /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).