From: Anton Bachin <antronbachin@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] [ANN] Bisect_ppx 1.3.0 – code coverage for OCaml
Date: Thu, 17 Aug 2017 13:30:33 -0500 [thread overview]
Message-ID: <0ED016A0-3D07-4BAE-A9FA-3A5F23F2E14E@gmail.com> (raw)
Greetings,
We are pleased to announce release 1.3.0 of Bisect_ppx, the OCaml code
coverage tool. Bisect_ppx generates nice reports, showing which parts of
your code are not tested:
https://github.com/aantron/bisect_ppx
See the release changelog:
https://github.com/aantron/bisect_ppx/releases/tag/1.3.0
This release improves compatibility with Jbuilder. Instructions are
available here:
https://github.com/aantron/bisect_ppx/blob/master/doc/advanced.md#Jbuilder
We have also changed the license from GPL 3.0 to the considerably more
permissive MPL 2.0. MPL allows Bisect_ppx to be incorporated into
proprietary projects. Basically, the only thing users have to do is
publish Bisect_ppx files if
1. they have been modified, and
2. they, or a project incorporating them, is being released.
For publishing, it is sufficient to contribute back to the project, host
a public fork (e.g. on GitHub), or simply include in your larger
project, if that project is open-source.
MPL 2.0 allows private use of modified Bisect_ppx. In practice, you
generally wouldn't release code instrumented with Bisect_ppx anyway, so
this means you can use Bisect_ppx as if it was under a typical
fully-permissive license without worrying about any copyleft
requirements.
If you are a user of the Bisect_ppx Ocamlbuild plugin, you should depend
on the new bisect_ppx-ocamlbuild OPAM package. It contains an ocamlfind
package of the same name, which is a replacement for the current
bisect_ppx.ocamlbuild. bisect_ppx.ocamlbuild will be removed in a future
release.
The Ocamlbuild plugin remains dedicated to the public domain.
Happy testing!
- The maintainers of Bisect
reply other threads:[~2017-08-17 18:30 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=0ED016A0-3D07-4BAE-A9FA-3A5F23F2E14E@gmail.com \
--to=antronbachin@gmail.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;
as well as URLs for NNTP newsgroup(s).