|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] dns, conduit, cohttp: hit the release train
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: > <snip> > 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. Anil > > 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 MirageOS-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |