From: Anton Bachin <antronbachin@gmail.com>
To: "caml-list@inria.fr users" <caml-list@inria.fr>
Subject: [Caml-list] [ANN] Lwt 2.6.0 – monadic concurrency library (resend)
Date: Fri, 28 Oct 2016 11:27:33 -0500 [thread overview]
Message-ID: <D40EE929-3D1F-409C-BE94-F66A019B7531@gmail.com> (raw)
[Apologies – resending due to problems with email address]
Greetings,
I am pleased to announce the 2.6.0 release of Lwt.
https://github.com/ocsigen/lwt
This release fixes several serious longstanding bugs (see changelog
[1]). The primary work, however, is towards making Lwt easier to
contribute to and maintain. To this end:
- Lwt is now automatically tested on OS X, Cygwin, and Windows, in
addition to Linux, with more platforms planned,
- there are documentation improvements,
- more test cases are being written,
- there is an initial plan/roadmap page, to be updated with your input
[2].
- a Gitter chat has been added [3],
- the issue backlog has been drained somewhat.
The next minor release, 2.7.0, will drop support for OCaml 4.01, and
begin a process of deprecating and very gradually removing obsolete
functions and modules, such as the Camlp4 syntax. This will yield a
smaller Lwt that is easier to understand. [ocaml.deprecated] attributes
will also make it safer to make desirable API changes.
A major near-term goal is to write more thorough documentation for Lwt,
and make Lwt easier to get started with. Please comment on omissions,
misleading parts, etc. (see contact [4]).
After addressing that, ordinary work will focus on quality of the
internals and API, especially with regard to performance.
Comments, issues, and contributions on any subject are welcome :)
Regards from new maintainer,
Anton
[1]: https://github.com/ocsigen/lwt/releases/tag/2.6.0
[2]: https://github.com/ocsigen/lwt/wiki/Plan
[3]: https://gitter.im/ocaml-lwt/Lobby
[4]: https://github.com/ocsigen/lwt#contact
reply other threads:[~2016-10-28 16:27 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=D40EE929-3D1F-409C-BE94-F66A019B7531@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