[MirageOS-devel] 2.0 releases going into mirage-dev

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

I've started tagging all the libraries currently in mirage-dev and have 
uploaded releases of most of them to https://github.com/mirage/mirage-dev. 

Next steps:
- add constraints on packages that would conflict (mostly cohttp) in the main 
opam repo

- figure out why this ocaml-dns downgrade happens only on 4.02: 
https://travis-ci.org/mirage/ocaml-dns/jobs/39791629#L265

Interesting question is what we do with mirage-dev now.  Should we instruct 
people to remove it?  It's actually more useful it seems to have remotes for a 
specific purpose (mirage/mirage-2-release) so that once they're done, they just 
contain archives.

If we bump mirage/mirage-dev to the git versions again, then users will always 
get the bleeding edge...

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel