caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.01.0 RC1
Date: Mon, 2 Sep 2013 17:12:08 +0100	[thread overview]
Message-ID: <0EFC93B8-B1FC-4A75-A7E8-5C274664AE6D@recoil.org> (raw)
In-Reply-To: <AE374225-7256-4AA7-B440-9E4C6EA541E4@inria.fr>

On 2 Sep 2013, at 15:23, Damien Doligez <damien.doligez@inria.fr> wrote:

> The release of OCaml version 4.01.0 is imminent.  We have
> created a release candidate for your testing pleasure.  Please
> download the sources, compile, install, and test your favourite
> software with it (or try it with OPAM).  Then let me know
> whether it works for you.

For the OPAM users among you, I've added a 4.01.0 compiler switch
which will track the RC releases, and eventually become the official
release when it's out.

$ opam update
$ opam switch 4.01.0
$ eval `opam config env`
# ???
# profit

I've been running a full regression test of the entire OPAM database
on a variety of architectures and triaging the results.  If anyone
else is interested in helping submit patches to fix issues, then
please see:
https://github.com/OCamlPro/opam-repository/issues/1029

Note that the above link is a bit raw, since it also includes failures
from bugs in 4.00.1 packages too.  We've just been fixing everything
we can spot in preparation for testing the forthcoming OPAM 1.1 beta
on as stable a package database as possible.  I'm preparing a blog
post describing the most common failures we've seen to help package
authors avoid them in the future (warnings-as-errors, I'm looking at
you!)

cheers,
Anil


      reply	other threads:[~2013-09-02 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 14:23 Damien Doligez
2013-09-02 16:12 ` Anil Madhavapeddy [this message]

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=0EFC93B8-B1FC-4A75-A7E8-5C274664AE6D@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@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).