On Sep 9, 8:04 pm, Sean Corfield <seancorfi...@gmail.com> wrote: > On Fri, Sep 9, 2011 at 1:09 AM, Jan Rychter <jrych...@gmail.com> wrote: [...] > > I think issues like that are fundamentally important if Clojure is to > > be adopted for production work. > > I agree - which is why I'm pushing on clojure-dev for some serious > attention to be paid to the contrib migration issue.
Thanks for the explanations. I'll summarize: clojure-contrib is being reorganized. There is no clear migration path for applications that use the monolithic 1.2 contrib. Not all of 1.2 contrib code made its way into new modules yet. There is no migration guide for existing applications. Unless clojure 1.3 can be used with 1.2 monolithic contrib, I'd strongly suggest that the release of clojure 1.3 should wait until the contrib situation is resolved. I'd much rather see an announcement of production-ready Clojure 1.3 than an announcement of very cool core code that can't really be used in production systems. Much as it sounds boring, it's the libraries that define the applicability and usability of a programming language. --J. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
