caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <damien.doligez@inria.fr>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Status and schedule of the 4.03.0 release
Date: Fri, 27 Nov 2015 14:06:51 +0100	[thread overview]
Message-ID: <A510E666-DC47-47C6-B195-6F2A687581E6@inria.fr> (raw)

Dear OCaml users,

Here is a summary of what's going on with the next release of OCaml:

We had a developer meeting on Nov 18 to decide which features will
go into the next release. As far as large features are concerned,
the set is now fixed. In addition to what's already in the Changes
file, we'll have:

- named constructor arguments (aka inline records)
- compiler annotations for performance (@tailcall @inline @unbox @noalloc...)
- flambda: major changes in the compiler pipeline
- GC improvements: no more large GC pause times
- Ephemerons: a generalization of weak pointers
- Ocamlbuild: spin off as an independent project

Note that, while they are still in Changes at the moment, we
have decided to remove the user-defined indexing operators
( .() .()<- etc. ) for the moment, because they clash with
another planned feature. They will probably be back in some
form in 4.04.

Our planned schedule is as follows:
- December: merging features
- December 20: end of merge window, creation of 4.03 branch,
  beta version.
- January: debugging
- early February: release

We are also planning to release an alpha version of the multicore
system as an OPAM switch shortly after the 4.03.0 release.

We are working hard on this release, and we need the cooperation of
all OCaml programmers, especially library authors: test your code on
trunk, adapt to the (few) incompatible changes, report bugs as early
as you can.

Happy hacking,

-- Damien


             reply	other threads:[~2015-11-27 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 13:06 Damien Doligez [this message]
2015-11-27 15:20 ` William
2015-11-27 16:22   ` François Bobot

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=A510E666-DC47-47C6-B195-6F2A687581E6@inria.fr \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@inria.fr \
    /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).