+1 We have production code here and would like to see 1.3 out even if the contrib issue resolve itself later. The first stable release of 1.3 needs to get used as widely as possible.
If some issues emerge in 1.3 it would be better to know it as early as possible. There are significant blocks of the old contrib available under the new modular structure to create apps based on 1.3. 1.3 will not be left on the shelf waiting for the outcome of this issue, it will be used. That's the ultimate test :) Luc P. On Sat, 10 Sep 2011 10:50:16 -0400 David Nolen <dnolen.li...@gmail.com> wrote: > On Sat, Sep 10, 2011 at 5:59 AM, Jan Rychter <jrych...@gmail.com> > wrote: > > > 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. > > > Waiting for contrib authors to sort out their libraries seems > unrelated as to whether 1.3 should or should not be released. That's > like delaying Python 3 because libraries don't support it yet. It > still wouldn't be released. > > David > -- Luc P. ================ The rabid Muppet -- 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
