From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id A26E37FC18 for ; Tue, 17 Feb 2015 01:36:22 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of louis.gesbert@ocamlpro.com) identity=pra; client-ip=37.187.244.36; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="louis.gesbert@ocamlpro.com"; x-sender="louis.gesbert@ocamlpro.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of louis.gesbert@ocamlpro.com) identity=mailfrom; client-ip=37.187.244.36; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="louis.gesbert@ocamlpro.com"; x-sender="louis.gesbert@ocamlpro.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@vps119294.ovh.net) identity=helo; client-ip=37.187.244.36; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="louis.gesbert@ocamlpro.com"; x-sender="postmaster@vps119294.ovh.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0ClBgCsi+JU/yT0uyVbgwZkA8Yngk8CCIEKRAEBAQEBAXyEDQEFGCI/EAsYCRMCEA8BRzQDiBPOOQEBCCKLDIRtBxYag3oFijmhQyKDfS+CdAEBAQ X-IPAS-Result: A0ClBgCsi+JU/yT0uyVbgwZkA8Yngk8CCIEKRAEBAQEBAXyEDQEFGCI/EAsYCRMCEA8BRzQDiBPOOQEBCCKLDIRtBxYag3oFijmhQyKDfS+CdAEBAQ X-IronPort-AV: E=Sophos;i="5.09,591,1418079600"; d="scan'208";a="100280745" Received: from 36.ip-37-187-244.eu (HELO vps119294.ovh.net) ([37.187.244.36]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 17 Feb 2015 01:36:21 +0100 From: Louis Gesbert To: opam-devel@lists.ocaml.org Cc: Adrien Nader , Anil Madhavapeddy , Ocaml Mailing List Date: Tue, 17 Feb 2015 09:36:17 +0900 Message-ID: <3079011.QOsAmGbPEa@agaric> Organization: OCamlPro In-Reply-To: <20150216185248.GA18316@notk.org> References: <20150216185248.GA18316@notk.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Validation-by: louis.gesbert@ocamlpro.com Subject: Re: [Caml-list] [opam-devel] OPAM: retiring 3.12.1 testing? Thanks a lot for the detailed overview. I was indeed thinking it wouldn't be worth keeping both 4.02.0 and 4.02.1, but didn't know, for example, about 4.00.1. The first consequence of dropping e.g. support for 3.12.1 would probably be that incompatible packages are either not fixed, or not declared incompatible, which would lead to an error during compilation whenever OPAM tried to install them, instead of a clear message or a solution around that package/version if it exists. Currently, according to the metadata, 561 of the 837 OPAM packages (67%) can be installed on 3.12.1, around 30 of which not at their latest version. The others either are not compatible or depend on an incompatible package. OPAM itself (as opposed to the repo) will obviously keep compiling on 3.12.1 for the moment (the tests regularly help pick up an incompatible String.init or likewise) Best, Louis Gesbert -- OCamlPro > - Adrien Nader, 16/02/2015 19:52 - > Hi, > > On Mon, Feb 16, 2015, Anil Madhavapeddy wrote: > > Dear OCaml list, > > > > 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 > > > > We will shortly have to test 4.02.1, and would also like to test trunk snapshots of the > > compiler as an "allowed failure". > > > > 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. > > > > Before we do this, I'd like to get a sense for how many people still care about ensuring > > that their packages work well on the 3.12.1 series, or if there are still distributions > > for which this support matters. If there is still sufficient interest, we can continue > > to support 3.12.1 for some time. > > For yypkg/win-builds I've done a quick survey of what's in Linux > distributions. I was mainly interested in moving past 3.12.1 > compatibility for my own code but found it undoable before the end of > this year or maybe early next year. > > Ubuntu 12.04 has 3.12.1 and is still supported and widespread. 14.04 has > 4.01.0 but isn't very old. Debian has a similar combination for its > versions. I think 4.02.0 wasn't picked by linux distributions with > long-term support (including RH if I'm not mistaken). > > 3.12.1 is really widespread and I think it has to be kept for a fairly > long time. 4.00.0 is basically never used. 4.01.0 is widespread and will > be widespread for some time. 4.02.0 is nowhere to be seen. I believe > 4.02.0/1 and maybe 4.02.2 won't be picked up either (unless 4.03.0 takes > close to two years to be released). > > I'd say: keep 3.12.1, 4.01.0, 4.02.whatever-is-the-most-recent (because > that's what ocamlers use) and trunk. Dump the others (i.e. 4.00.1, > 4.02.0). > >