Tim Watson

> The latest build failure is happening because the latest exit/catchExit changes have not been released by distributed-process, or so it seems. Hmn, you're quite right. I think I'll hack...

> Whether or not we release a new version of CH any time soon should be irrelevant to this discussion. It's not unlikely > that distributed-process-platform will continue to depend...

Also.... It would be nice if travis-ci supported multiple versions of ghc and custom dependencies. We could use virthualenv to achieve this (for multiple ghc versions) or cabal-dev for custom...

> That would be Well-Typed, and we're okay with it. Let me know. Ok yes please @edsko. I'll probably have to migrate the issue tracker data by hand (urgh) but...

I'm not sure that's really true, but I have added you as a collaborator nonetheless. Let me know if it works! :)

I've moved the repo to my own org and given you admin rights so maybe try again?

Yes let's go for it - this way the issues will be transferred across which works nicely for me.

Nope, that's all you need to do.

@edsko - I'm no longer a repo admin - is that something you can fix? > In terms of using git-flow I'm going to switch to the following scheme: Production:...

Erm @edsko I don't seem to have commit rights any more either. Eek! :/