On Tue, Dec 24, 2013 at 7:23 AM, <solo.l...@gmail.com> wrote: > Yes, after looking into this, upgrading the libraries before upgrade the > Clojure version is unfeasible in our case. I prefer not to keep a 1.2 > environment around forever but take our time phasing it out to avoid service > disruption. I think the dual environment consensus here is the way to go.
Please keep us posted on how this goes - I think it's an interesting case study for what happens with a large legacy code base. Fortunately the 1.2 -> 1.3 changes were the biggest we've had to deal with so far and all the signs indicate we won't have to deal with that again, so this is a pain that only early adopters will be feeling. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
