And given that ClojureScript itself is still on a 0.0-nnnn version number, I don’t think I’d consider it any more "released" than the official alpha / beta builds of Clojure 1.7.0 that are also on Maven Central…
That said, we’ve been running 1.7.0 in production for quite a while — we’ve had Beta 1 in production since April 15th with no issues, and had Alphas in production before that. Sean On May 11, 2015, at 3:34 PM, Sean Grove <[email protected]> wrote: > Honestly curious what you mean by "compile clojurescript snippets on the > fly", and why you're not able to stay on the current ClojureScript version > until Clojure 1.7 is stable/released - is there a bug/security/feature in a > library that's switched over that's forcing your hand? > > On Mon, May 11, 2015 at 3:27 PM, Stephen Nelson <[email protected] > <mailto:[email protected]>> wrote: > > As I said above, you must specify Clojure 1.7.0-beta2 as your Clojure > > dependency. > > We're quite unhappy about this change. Wherever possible, we try to > avoid using unreleased software in our production environments, but > because we compile clojurescript snippets on the fly we're now forced > to switch our whole project to 1.7. > > Could you please consider reverting the clj->cljc change until 1.7 is > released, or maintaining a 1.6-compatible branch for bug fixes. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
