Prepare the 0.3.0 release.

[yallop]

No description provided.

[dsheets]

This may need some more changelog entries?

[yallop]

What do you have in mind?

[dsheets]

Fcntl_unix, Fcntl_unix_lwt? Maybe we should call Fcntl_unix_lwt just Fcntl_lwt because the data types and conversions alone will never have reason to use lwt without a system for I/O?

[yallop]

Fcntl_unix was in 0.2.0. The lwt binding is already mentioned, but I'll add a reference to the module.

I don't have strong views about the name Fcntl_unix_lwt. I think the _unix_lwt suffix indicates that it's more closely related to Fcntl_unix than to Fcntl, and that it won't be available on non-Unix systems, even those (such as js_of_ocaml) that support lwt, but I'll rename it if you prefer; let me know either way.

[dsheets]

No, that all makes sense, thanks!