Fork me on GitHub
#test-check
<
2019-03-03
>
borkdude15:03:29

The last stable release of test.check has been 12 NOV 2015. What are the alpha releases waiting for to become stable?

gfredericks15:03:02

a set of milestones I was asymptotically approaching for a while; most of them I gave up on, so the only reason I haven't cut a release is because of the things that seem too half-baked to release

gfredericks15:03:46

I think the tickets tagged 0.10.0 reflected what I hadn't yet given up on

gfredericks15:03:56

now that I look, it seems like it's just a documentation ticket

gfredericks15:03:39

the big thing I wanted to do was write some guides, but that was apparently too much work, and arguably isn't related to a release

gfredericks15:03:37

I think I also wanted to sync up with alex w.r.t. spec, and see if there was anything that'd be super useful to change before a release

gfredericks15:03:59

so that there aren't future compatibility issues

borkdude15:03:27

did the lazy loading of generators in spec require changes to tc?

gfredericks15:03:43

no, but there was a change to gen/such-that for spec

borkdude15:03:12

is spec itself still using 0.9.0?

gfredericks15:03:38

I guess? but if you depend on 0.10.0 yourself, that's what it'll be using

gfredericks15:03:46

so people will conceivably be combining arbitrary pairs of versions

borkdude15:03:41

so 0.9.0 already had a change to gen/such-that for spec in November 2015?

borkdude15:03:07

It seems not.

gfredericks15:03:52

yeah, I didn't mean to imply that

gfredericks16:03:16

I'll put out another alpha release this week for the cljs changes, and then I will plan on talking to alex in a few weeks when my free time clears up

borkdude16:03:54

yeah, no hurry, just wanted to know the current state

👍 5