From: "François Bobot" <francois.bobot@cea.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OPAM: retiring 3.12.1 testing?
Date: Mon, 16 Feb 2015 16:59:21 +0100 [thread overview]
Message-ID: <54E213D9.6030705@cea.fr> (raw)
In-Reply-To: <DA83A128-9AA1-4AB4-84FE-9762A9AB0C7C@recoil.org>
On 16/02/2015 12:04, Anil Madhavapeddy wrote:
> We are currently testing the following compiler versions on every pull request to OPAM;
>
> - OCaml 3.12.1
> - OCaml 4.00.1
> - OCaml 4.01.0
> - OCaml 4.02.0
>
>
> Running 6 compiler revisions per package puts quite a bit of stress on our Travis CI
> resources, and so it's probably time to retire OCaml 3.12.1 from the testing matrix.
>
More than 3.12.1, I think 4.02.0 should retire when 4.02.1 enter.
OCaml 4.02.1 added a lot of important fixes, I think nobody should use 4.02.0 instead of 4.02.1.
Best,
--
François Bobot
next prev parent reply other threads:[~2015-02-16 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 11:04 Anil Madhavapeddy
2015-02-16 11:21 ` Török Edwin
2015-02-16 11:25 ` Anil Madhavapeddy
2015-02-16 15:59 ` François Bobot [this message]
2015-02-16 16:09 ` Gabriel Scherer
2015-02-16 18:22 ` Stephen Dolan
2015-02-16 18:52 ` Adrien Nader
2015-02-17 0:36 ` [Caml-list] [opam-devel] " Louis Gesbert
2015-02-17 7:15 ` [Caml-list] " Anil Madhavapeddy
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=54E213D9.6030705@cea.fr \
--to=francois.bobot@cea.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