From: Mindy <mindy@somerandomidiot.com>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] mirage 3.0.0
Date: Thu, 23 Feb 2017 11:33:01 -0600 [thread overview]
Message-ID: <cdc02bfb-23e0-fab6-aecd-bd06d5533c7d@somerandomidiot.com> (raw)
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
next reply other threads:[~2017-02-23 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 17:33 Mindy [this message]
2017-02-23 18:04 ` Anil Madhavapeddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cdc02bfb-23e0-fab6-aecd-bd06d5533c7d@somerandomidiot.com \
--to=mindy@somerandomidiot.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox