@alexmiller: should we also have a direct-linking=true config on contrib test matrices?

I've started working on that. It's more complicated and affects a lot more people.

@bronsa: hey, any chance you could update the dependencies in tools.analyzer.jvm on the next release to newest core.memoize and tools.reader?

sure

also, wondering if you plan to do a 1.0 for tools.reader ?

noticed the 0.10 numbers... :)

after some more cljs testing, possibly

what's the procedure for 1.0 contrib btw?

IIRC Rich has to approve it?

as far as I'm concerned it's up to you

I don't think Rich has to approve it

you're the project maintainer and I consider you to be the judge of its 1.0-ness

@alexmiller: I was remembering what's written here http://dev.clojure.org/display/community/Contrib+1.0.0+Releases

Specifically "The first release of a contributed library with a major version number of "1" requires approval by Clojure/core."

I think tools.reader passes that bar

well then I guess we'll have 1.0 soon

as a member of Clojure/core I approve it :)

@alexmiller: to be more clear about the eastwood issue wrt :rettag -- it's not a clojure bug. I just don't want (nor do I want @andy.fingerhut) to waste any amount of time changing code to account for what seems to be a worthless change

and if you know how I feel about the tag/type-hinting situation in clojure, you'll understand why I'm this bothered about it

sure

@alexmiller: it looks like t.a.jvm already depends on the last core.memoize

ah, you're right

I mis-read the commit log for core.memoize

looks like it needs a release, which vaguely reminds me of the last time I worked on this

if only I remembered anything else about it :)

guess I'll throw that one on the pile :)

@bronsa: ok, so I was actually right - there core.memoize 0.5.7 was released in January (by me) but I never updated the readme

but I have now done so

ah, that's what it was then

ok I'll update the dependency

thx!