John Lato wrote:

According to http://packdeps.haskellers.com/reverse, test-framework has over 300 reverse dependencies (and tasty has 12). Given that ghc-7.8 will be out relatively soon, why break all of them?

I agree. Would it not make more sense to start maintaining test-framework as part of the haskell-pkg-janitors group [0] on github and uploading a new fixed version ASAP? Erik [0] https://github.com/haskell-pkg-janitors -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

(Disclosure: I'm the author of tasty.) If there are people who are willing to keep test-framework on life support, it's definitely useful. Let's keep those revdeps from breaking. However, if someone is considering adding new features, I'd encourage them to look at tasty instead. It has a cleaner and smaller code base and is more extensible, but otherwise is very similar in spirit to test-framework. Roman * Greg Weber [2013-10-08 20:03:36-0700]

sorry, I didn't understand what the original message was about. I was talking about a long-term direction

On Tue, Oct 8, 2013 at 7:09 PM, Bryan O'Sullivan wrote:

...

I don't really care about that goal, to be honest; in this case, I just want a minimal number of existing packages to break when GHC 7.8.1 is released.

On Tuesday, October 8, 2013, Greg Weber wrote:

...

I would like to reduce the amount of test framework fragmentation. A better path forward might be to use the newer more extensible and well maintained tasty package. I am imagining it is trivial to create a compatibility layer with the previous test-framework or to find and replace, but that might not be the case.

* Gregory Collins [2013-10-09 08:16:06-0700]

On Wed, Oct 9, 2013 at 1:04 AM, Roman Cheplyaka wrote:

...

However, if someone is considering adding new features, I'd encourage them to look at tasty instead. It has a cleaner and smaller code base and is more extensible, but otherwise is very similar in spirit to test-framework.

Why don't you try to make this work as api-compatible with the old test-framework as possible and release it as test-framework-1.0.0.0?

Why would I do that? Tasty is now a separate package, with its own API and its own users. Why would I break it? People who continue to use test-framework are presumably happy with it, so maintenance releases by Bryan or haskell-pkg-janitors should be enough for them. If they ever feel that tasty is better for them, it won't take much effort to switch. Roman