Opam package still points to ocamlforge

[smondet]

http://opam.ocaml.org/packages/release/release.1.1.1/
that + the fact that "ocaml release" is not search-engine-friendly makes the project look dead until we find this repo.

PS: do you have timeline for cutting a release ☺?

[andrenth]

Hi Sebastian

I'll update the URL for the next version.

I had some plans for 2.0 that included the following

1. Support for either Lwt or Async
2. Switch release_config to Menhir
3. Provide support for multiple configuration formats (I'd like to maybe
   switch ini format to TOML and also support something like UCL)
4. File descriptor passing in Release IPC (Lwt provides this but Async
   didn't last time I looked)
5. Whatever else came to my mind

Of those I only had time to work on 1), though I think 2) would be easy
enough if 3) is ignored.

Although I didn't have an opportunity to test release_async, I believe the
code should be good enough for a 2.0.0 release.

What do you think? Have you been using Release in production? Is there
anything you'd like to see in the framework?

Best,
Andre

On Wed, Jul 27, 2016 at 6:07 PM, Sebastien Mondet notifications@github.com
wrote:

http://opam.ocaml.org/packages/release/release.1.1.1/
that + the fact that "ocaml release" is not search-engine-friendly makes
the project look dead until we find this repo.

PS: do you have timeline for cutting a release ☺?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#8, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB2BY7uPMaDqD43-_XGGoCEoOSLBV7Mks5qZ8isgaJpZM4JWoUX
.

[smondet]

Thanks for the update!

I'm not using the library (yet?), I am just exploring options for a new project.
That's how I came across the ocamlforge website and much later by chance across this repo :)