Thanks, Alex. I agree that migrating these tiny 1.2 applications would be wasted effort as the majority won't change and will become obsolete soon anyway.The ones which will remain relevant will be easy to identify and may be worth migrating.
Regarding testing, no, I have no confidence in these reports being well tested and I'm taking a very defensive stance against them. My view is they function adequately in their 1.2 bubble with all the copying and pasting with a slim chance of surviving outside of that. I've written a lengthy blog post on our internal forum on how to proceed. Basically, it's as follows: 1) Analysis: which contrib libraries we use, how we use them, and rank them accordingly. Find their 1.5 analogues or best alternative. 2) Get a 1.5 environment up and running for only our immediate team. The outside world will keep creating reports for the 1.2 environment. 3) Create a number of sample reports for the 1.5 environment and write a few educational docs. 4) Once the samples are done, update the report editor such that all new reports must conform to 1.5 standards. Old 1.2 reports will still be accessible. 5) 12 months after step 4, check which 1.2 reports are still being invoked. Migrate them, test them, and then shutdown the 1.2 environment. On Tuesday, December 24, 2013 2:46:08 PM UTC-5, Alex Baranosky wrote: > > Hi Solo, > > I did a big migration from 1.2 to 1.5 at work this past February. Here > are a few of the things that I gleaned from that experience, i addition to > the great advice mentioned already in this thread: > > * with 1000's of these applications, I'd take the approach of only > migrating to 1.5 when there's a change needed, because there's a good > chance a lot of them will never need to be modified. Any extra apps you > need to migrate could be work down the drain. > * on the other hand, you can get a nice groove going, and may want to do a > bunch of reports in one go. The changes you may find can be repetitive. > * to make sure you are only including namespaces that absolutely need to > be used by your application, AND to convert the ns declarations into 1.5 > format automatically I used https://github.com/technomancy/slamhound. > Watch out for any macro-heavy code though, because Slamhound can miss > dependencies used exclusively in macros. > * are these reports tested? If not well tested be wary, because there were > a lot of number-related changes from 1.2 to 1.3 > * keep an eye out for duplicated patterns in the reports. If there are > some common pieces you might be able to just migrate those to 1.5 and use > them as a library for the other reports. YMMV. > * > > Best, > Alex > > On Tue, Dec 24, 2013 at 10:48 AM, Sean Corfield > <seanco...@gmail.com<javascript:> > > wrote: > >> On Tue, Dec 24, 2013 at 7:23 AM, <solo...@gmail.com <javascript:>> >> 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 clo...@googlegroups.com<javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> 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+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- 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.
