caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Refis <trefis@janestreet.com>
To: ocaml-core@googlegroups.com, caml-list@inria.fr
Subject: [Caml-list] [ANN] Core Suite 113.33
Date: Thu, 14 Apr 2016 15:02:49 +0100	[thread overview]
Message-ID: <CAG2_RL02WxaW-SmXsiqjozGNVYDSD28kQWzGTHQqDWSADcR9TQ@mail.gmail.com> (raw)

I am pleased to announce the 113.33 release of the Core suite.

All packages are now in opam and the API documentation is here:

    https://ocaml.janestreet.com/ocaml-core/113.33/doc/

Notable changes for this release include:

    - compatibility with OCaml 4.03
    - a new package: incremental_kernel. A subset of our incremental
library depending only on core_kernel.

The full changelog for this release can be found here:

    https://ocaml.janestreet.com/ocaml-core/113.33/CHANGES.html

The following packages were upgraded:

- async
- async_extended
- async_extra
- async_find
- async_inotify
- async_kernel
- async_parallel
- async_rpc_kernel
- async_shell
- async_smtp
- async_ssl
- async_unix
- bignum
- bin_prot
- core
- core_bench
- core_extended
- core_kernel
- core_profiler
- email_message
- incremental
- incremental_kernel
- jenga
- ocaml_plugin
- patdiff
- patience_diff
- ppx_assert
- ppx_bench
- ppx_bin_prot
- ppx_compare
- ppx_conv_func
- ppx_core
- ppx_csv_conv
- ppx_custom_printf
- ppx_driver
- ppx_enumerate
- ppx_expect
- ppx_fail
- ppx_fields_conv
- ppx_here
- ppx_inline_test
- ppx_jane
- ppx_let
- ppx_optcomp
- ppx_pipebang
- ppx_sexp_conv
- ppx_sexp_message
- ppx_sexp_value
- ppx_type_conv
- ppx_typerep_conv
- ppx_variants_conv
- ppx_xml_conv
- re2
- rpc_parallel
- sexplib
- textutils
- typerep_extended

                 reply	other threads:[~2016-04-14 14:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAG2_RL02WxaW-SmXsiqjozGNVYDSD28kQWzGTHQqDWSADcR9TQ@mail.gmail.com \
    --to=trefis@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=ocaml-core@googlegroups.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).