From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] [ANN] OASIS v0.4.0
Date: Fri, 13 Dec 2013 03:23:17 +0100 [thread overview]
Message-ID: <CAOCAUGMVm91xukLqe2DSZM+ncvu+cqC_8EwhXLCEQrWzwyHM+Q@mail.gmail.com> (raw)
Hi all,
I am pleased to announce that OASIS v0.4.0 has been released.
This new release contains a lot of fixes contributed by users who
kindly send me back their patches and pull-request.
* Migrate the source repository to https://github.com/ocaml/oasis
* Fix a lot of code style issues (e.g. blank at the end of the line)
and create a test to check that the style of generated files is
correct. Some related tools has been fixed asi well, for the best
formatting use ocamlmod >= 0.0.7 and ocaml-data-notation >= 0.0.10.
* Port all tests to OUnit 2.0, which allows to run all tests faster.
* Run some tests with a fake bytecode only setup, so that we can
always check that bytecode and nativecode tests are passing. (Closes:
#1306)
* Fix a missing dependency on ocamlbuild package and inclusion of
ocambuildlib.cma in builtin-plugins.cma.
* Introduce a framework to create features.
* Add fields AlphaFeatures and BetaFeatures to list the experimental
features you want to use in your _oasis
* Using AlphaFeatures and BetaFeatures is only allowed if OASISFormat
is set to the latest OASIS version. There is no backward compatiblity
for experimental features. For example, if you are using OASIS 0.4.X,
OASISFormat must be set to 0.4.
* AlphaFeatures represents features not fully completed that maybe
very unstable, quickly evolving and even removed in future release.
* BetaFeatures represents features almost finished that needs to
mature a bit before being published.
Read more of this announcement here:
http://le-gall.net/sylvain+violaine/blog/index.php?post/2013/12/11/Release-of-OASIS-0.4.0
reply other threads:[~2013-12-13 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOCAUGMVm91xukLqe2DSZM+ncvu+cqC_8EwhXLCEQrWzwyHM+Q@mail.gmail.com \
--to=sylvain@le-gall.net \
--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;
as well as URLs for NNTP newsgroup(s).