[Caml-list] [ANN] mirage 3.0.0

[Caml-list] [ANN] mirage 3.0.0

[Mindy]

Hello!

It is my great pleasure to announce that Mirage version 3 has been 
released into opam-repository.  Allowing for the time necessary to sync 
`opam.ocaml.org`, you should soon be able to upgrade to Mirage 3. You'll 
need to be using OCaml version 4.03.0 or later.

For more information on what's in Mirage 3, check out the blog post at 
https://mirage.io/blog/announcing-mirage-30-release . (There's also a 
version hosted on the new Solo5 backend at 
http://solo5.mirage.io/blog/announcing-mirage-30-release !)

We've prepared a porting guide at 
https://mirage.io/wiki/mirage2-to-mirage3 for those of you want quick 
help getting your unikernels up and running in the new universe.  The 
introductory content at https://mirage.io/wiki/hello-world (and 
https://github.com/mirage/mirage-skeleton , to which it refers) has also 
been updated, if you're looking to get started with Mirage for the first 
time.


If you choose to use a pre-existing opam switch when upgrading to Mirage 
3 from Mirage 2, you may need to remove some roots that were previously 
autoinstalled by `mirage configure` in version 2 before `opam upgrade` 
is willing to upgrade you to Mirage 3.

If you were using the `mirage-dev` or `mirageos-3-beta` opam remotes, 
those are no longer necessary.  `mirageos-3-beta` will be removed 
shortly, and `mirage-dev` will have its packages cleared to make way for 
whatever next set of staging packages is about to dazzle us.

Please let us know if you have any difficulties or questions :)

Thanks,

Mindy Preston

Re: [Caml-list] [ANN] mirage 3.0.0

[Anil Madhavapeddy]

On 23 Feb 2017, at 17:33, Mindy <mindy@somerandomidiot.com> wrote:
> 
> Hello!
> 
> It is my great pleasure to announce that Mirage version 3 has been released into opam-repository.  Allowing for the time necessary to sync `opam.ocaml.org`, you should soon be able to upgrade to Mirage 3. You'll need to be using OCaml version 4.03.0 or later.
> 
> For more information on what's in Mirage 3, check out the blog post at https://mirage.io/blog/announcing-mirage-30-release . (There's also a version hosted on the new Solo5 backend at http://solo5.mirage.io/blog/announcing-mirage-30-release !)
> 
> We've prepared a porting guide at https://mirage.io/wiki/mirage2-to-mirage3 for those of you want quick help getting your unikernels up and running in the new universe.  The introductory content at https://mirage.io/wiki/hello-world (and https://github.com/mirage/mirage-skeleton , to which it refers) has also been updated, if you're looking to get started with Mirage for the first time.

And to the more experienced OCaml'ers, one of the more exciting aspects of switching to a baseline of OCaml 4.03 is that we can finally start taking advantage of new features such as flambda now.  The executable part of a typical Mirage unikernel is a set of functor applications that link in the relevant device drivers, and so we're hoping to see a real performance and efficiency benefits from the compiler.

So if you are interested in this sort of topic, we'd love to help you get involved and to contribute. Many of the libraries (see http://docs.mirage.io) can run just fine in a normal Linux or macos laptop, without requiring a hypervisor, and the vast amount of development is using a normal OCaml development environment.

regards,
Anil