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 BB5097F91C for ; Mon, 23 May 2016 11:39:57 +0200 (CEST) IronPort-PHdr: 9a23:oeNwtB0Aj9C49CD7smDT+DRfVm0co7zxezQtwd8ZsegQLvad9pjvdHbS+e9qxAeQG96LurQf2qGP7ejJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6kO74TNaIBjjLw09fr2zQd6DyZ/mnLnss7ToICx2xxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cY6Lod8JsKWqz/e+E8TKdEJDUgKWE8osPx/1GXRgKK4j4YU34KuhtOGQnMqh/gCMTfqCz/48hwwiSfPMC+YbExWDKlp/NpRB7tiSEAHzww9mzMltZ9gb4dqxWk8U8si7XIaZ2YYaItNpjWeskXEDJM Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=jdimino@janestreet.com; spf=Pass smtp.mailfrom=jdimino@janestreet.com; spf=None smtp.helo=postmaster@mxout3.mail.janestreet.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jdimino@janestreet.com) identity=pra; client-ip=38.105.200.229; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jdimino@janestreet.com"; x-sender="jdimino@janestreet.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of jdimino@janestreet.com designates 38.105.200.229 as permitted sender) identity=mailfrom; client-ip=38.105.200.229; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jdimino@janestreet.com"; x-sender="jdimino@janestreet.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mxout3.mail.janestreet.com) identity=helo; client-ip=38.105.200.229; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jdimino@janestreet.com"; x-sender="postmaster@mxout3.mail.janestreet.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DkAACFz0JXduXIaSZdhA19Brl5AQ2BdRcBCoVvgScHOBQBAQEBAQEBAREBChYJRQuCLYIuER0BATgYBgc3AiQSAQUBIjWIDQMLlTSPQoExPjGKVGeEQQEBBYxRCwEBARsIEIYXiTmCHAstE4JGmDyBL4RRgniFKII3jGWODRIegQ8eAQGCOz+BNm2JQAEBAQ X-IPAS-Result: A0DkAACFz0JXduXIaSZdhA19Brl5AQ2BdRcBCoVvgScHOBQBAQEBAQEBAREBChYJRQuCLYIuER0BATgYBgc3AiQSAQUBIjWIDQMLlTSPQoExPjGKVGeEQQEBBYxRCwEBARsIEIYXiTmCHAstE4JGmDyBL4RRgniFKII3jGWODRIegQ8eAQGCOz+BNm2JQAEBAQ X-IronPort-AV: E=Sophos;i="5.26,354,1459807200"; d="scan'208,217";a="178673247" Received: from mxout3.mail.janestreet.com ([38.105.200.229]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 May 2016 11:39:56 +0200 Received: from tot-qpr-mailcore2.delacy.com ([172.27.56.106] helo=tot-qpr-mailcore2) by mxout3.mail.janestreet.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1b4mL4-0007zt-1a for caml-list@inria.fr; Mon, 23 May 2016 05:39:54 -0400 X-JS-Flow: external Received: by tot-qpr-mailcore2 with JS-mailcore (0.1) (envelope-from ) id BXQs_q-AAACkp-AU; 2016-05-23 05:39:54.011209-04:00 Received: from mail-io0-f200.google.com ([209.85.223.200]) by mxgoog1.mail.janestreet.com with esmtps (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.72) (envelope-from ) id 1b4mL3-0001OP-Uj for caml-list@inria.fr; Mon, 23 May 2016 05:39:53 -0400 Received: by mail-io0-f200.google.com with SMTP id 190so359601973iow.2 for ; Mon, 23 May 2016 02:39:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:date:message-id:subject:from:to; bh=C/G0/h66LmyY03cM0s8HPLH4wwJfl6RvXjEUgl8BCQU=; b=GIvDAdi2aY8JKfSTVWf3Jh4RitY80R4BVmLhLx1WM+5V81NHP/ArOtQL0tO/IybA6o vHUmi1Z0n3/lwT76hcXCtJ6J+cIKEyb0JCGm9LYn/v0aRAbVJ3yQff1lpUqSBzcaDTXf ANYhqCAjpBXXH2NJRkwA1GP9S5c7yIfeHVcRQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=C/G0/h66LmyY03cM0s8HPLH4wwJfl6RvXjEUgl8BCQU=; b=GcZX6o/CGFUXaJCNAHOY5jR+WO+2wplj1VzBxuortRld0yL9nhrMPpqxHhgunO7vZK guUyoengBU38NDks69Oln/uzypVj5p4MNdXbkW4KmhDVNtB8EEypNAmftY76lfX87EZS tIA7xSr/iAUvftWXnVnCc/nqWtYTwVCc4m2DYC2Y2Rf0XstwT8Bvz7lh49GYUnvGsT+R 0Z6L8ywMAxK1K6EeRrTNQjzS9T/T0oNTCwlkge4/y9IPxMXKKz96yLNajBxcrR7SMSJ0 PIjHkHe/ML686AUsPDQfDRiPTYCPnXoOfhY8IZnRApoH5Lk3yJWA+45Xn7pkHtPALeCi 0pzQ== X-Gm-Message-State: AOPr4FX3AFEU89rAKdoLE5sgMuxLF9AiuGeIhHYaX/DrHgY0iXZOBfl+9N10A5q8RI3alMXCHC8dQwk3zfTdymdKnsB5b3KHvJ9sWo1nE78efsiTxB127MJ9fCwbmNsbYG+GOCFbZLirPpyAx5TWhEbgrwyZFVDoAYiEJMJMj48= X-Received: by 10.107.165.12 with SMTP id o12mr13565451ioe.56.1463996393552; Mon, 23 May 2016 02:39:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.165.12 with SMTP id o12mr13565439ioe.56.1463996393309; Mon, 23 May 2016 02:39:53 -0700 (PDT) Received: by 10.50.128.37 with HTTP; Mon, 23 May 2016 02:39:53 -0700 (PDT) Date: Mon, 23 May 2016 10:39:53 +0100 Message-ID: From:Jeremie Dimino To:"caml-list@inria.fr" Content-Type: multipart/alternative; boundary=001a1141f340fa01bd05337f38ad X-JS-Processed-by: mailcore Subject: [Caml-list] More frequent pushes to Jane Street github repositories + janestreet/opam-repository --001a1141f340fa01bd05337f38ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, We are currently trying to improve our workflow for releasing our code =E2= =80=8Bon github =E2=80=8Band following up on external contributions. As a first step in this direction, w=E2=80=8Be reworked=E2=80=8B our intern= al process for =E2=80=8Bexporting=E2=80=8B the public release and we are now able to push = to github more often. =E2=80=8BSo going forward, instead of pushing one huge commit before= every =E2=80=8Bmajor release=E2=80=8B in the main opam repository=E2=80=8B, we wi= ll push smaller commits more frequently. This has several consequences: - it will be easier to follow the latest changes - accepted pull requests will appear in the git repository earlier - you can complain if we break your code before the next release in opam... =E2=80=8BInitially the commit messages will still be meaningless and the ch= angelogs might be slightly lagging behind given that producing them still requires a fair amount of work from a human.=E2=80=8B However, we are planning to impr= ove this over time. =E2=80=8BNote that we'll continue to provide support for the latest version= that is released in opam.=E2=80=8B ## =E2=80=8Bjanestreet/opam-repository To help trying the development version of our libraries, we've setup an opam repository that follows their latest development version [1]. So in order to try out the latest version of core, you can do: $ opam repo add git://github.com/janestreet/opam-repository.git =E2=80=8B =E2=80=8B$ opam install core =E2=80=8BPinning individual packages with `opam pin add --dev` might work a= s well, but there is no guarantee about it=E2=80=8B. ## 113.43+70 To start the new process, we just pushed the latest version of our code on github. The version is 113.43+70 and includes a fair amount of changes. [1] https://github.com/janestreet/opam-repository --=E2=80=8B =E2=80=8B Jeremie=E2=80=8B Dimino, for the Core team --001a1141f340fa01bd05337f38ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

We are currently trying = to improve our workflow for releasing our code =E2=80=8Bon github =E2=80=8B= and following up on external contributions.

As a f= irst step in this direction, w=E2=80=8Be reworked=E2=80=8B our internal pro= cess for =E2=80=8Bexporting=E2=80=8B the public release and we are now able= to push to github more often. =E2=80=8BSo going forward, instead of pushin= g one huge commit before every =E2=80=8Bmajor release=E2=80=8B in the main = opam repository=E2=80=8B, we will push smaller commits more frequently.

This has several consequences:

- it will be easier to follow the latest changes
- accepted pu= ll requests will appear in the git repository earlier
- you can c= omplain if we break your code before the next release in opam...
=
=E2=80=8BInitially the commit messages will still be meaning= less and the changelogs might be slightly lagging behind given that produci= ng them still requires a fair amount of work from a human.=E2=80=8B However= , we are planning to improve this over time.

=E2= =80=8BNote that we'll continue to provide support for the latest versio= n that is released in opam.=E2=80=8B

## =E2=80=8Bj= anestreet/opam-repository

To help trying the devel= opment version of our libraries, we've setup an opam repository that fo= llows their latest development version [1]. So in order to try out the late= st version of core, you can do:

=C2=A0 =C2=A0 $ op= am repo add git://github.com/janestreet/opam-repository.git
=E2=80=8B =C2= =A0 =C2=A0=E2=80=8B$ opam install core

=E2=80=8BPi= nning individual packages with `opam pin add --dev` might work as well, but= there is no guarantee about it=E2=80=8B.

## 113.4= 3+70

To start the new process, we just pushed the = latest version of our code on github. The version is 113.43+70 and includes= a fair amount of changes.


--=E2=80=8B =E2=80=8B
Jeremie=E2=80=8B Dimino, for the Core team
--001a1141f340fa01bd05337f38ad--