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

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

  • To: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Fri, 23 Jun 2017 13:17:49 +0100
  • Delivery-date: Fri, 23 Jun 2017 12:18:09 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; q=dns; s=selector1; b=Ag66W8+bLGZrR5OMVVqa0 A+i/DC5g820eZJVuiN8e4IzoaGTxtJwqv2Ugn/siHtF9lYMrfC4UdRya7RaWVVTc P/h5hWRDtPX6x0WoECIQmAI6rRZCC6GA6LJ8mEVVywWkCvHCGTNsseGdJ21LCoka zebG4YzdA1MmNJ4YB9zhJY=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

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 

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 

MirageOS-devel mailing list



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