[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] dns, conduit, cohttp: hit the release train

  • To: Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Fri, 23 Jun 2017 14:09:23 +0100
  • Cc: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 23 Jun 2017 13:09:31 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=AJFmAVtyfHkMhv5+viw/Xhw/EJRmS1BCnVXrfZlMarK1uVSGNYj 5+nyR4CskTqLNpFBVh3Rt53eP8kphsFKBBZA9BAdcm09+Dxh+XI9+z9mLYCBBGbe ILyIZ4zt9+7c/kk3kTUAZCJp5Giqz5tDB+vZ4QhWJgv+pg8u0/W2ftHw=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 23 Jun 2017, at 13:46, Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx> wrote:
> I am just cutting a new release of alcotest which will break some packages:
> I haven't reported all the constraints upstream yet, so would make sense to 
> double-check them. Also, that would be great to enable `install -t` in the CI 
> (or just set OPAMBUILDTEST=1 in the environment) as I spent the week fixing 
> test constraints which were pretty broken[1].

Ok, can you cut the release and put the new alcotest into mirage/mirage-dev and 
not the main repository?  I will install/upgrade the CI on mirage/mirage-dev to 
also run the tests in a separate build phase, and also run some bulk builds.


> Thomas
> [1]: 
> https://github.com/ocaml/opam-repository/pulls?q=is%3Apr+author%3Asamoht+is%3Aclosed
>  (2 pages)
>> On 23 Jun 2017, at 14:17, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>> We have got significant PRs active for DNS, Conduit, Cohttp and Charrua that 
>> port them all them all to use Jbuilder, in the master branches of the 
>> relevant repos.
>> This speeds up the build, removes the use of -pack in favour of module 
>> aliases, and also removes depopts.
>> Releasing them will require quite a few upper bounds, and so I am starting 
>> to cut releases and stage them in https://github.com/mirage/mirage-dev.
>> I have started with dns:
>> - https://github.com/mirage/ocaml-dns/releases/tag/v1.0.0
>> And will move onto Conduit next, and then Charrua, and then Cohttp.  Upper 
>> bounds will be placed in opam-repo for older versions, so we'll need to some 
>> work to port older packages to the new package layout.  When the upper 
>> bounds are in place in the opam repository, I will export the releases from 
>> mirage-dev to the stable upstream opam, and post on discuss.ocaml.org.
>> Is there anything else that needs to hit the build-system release train at 
>> this time?
>> thanks
>> Anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.