Thanks for all the great tips y'all! I will definitely look into deadwood--hadn't heard of it and it's got such a catchy name.
On the 7k, it's one of those things where they were like "yeah...you're gonna want to take care of that at some point." I was hoping to upgrade first and then remove some of the code either through core functionality or improved contribs--views 2 for example :). Expect another dev mailing list request in a couple of months on how to refactor monster modules.
I don't think there was much/any core hacking, but there was some contributed module hacking "somewhere".
Seriously though, it's working software made by really nice, really busy people. They recognize the limitations of the current state and want to take the time to migrate and create more maintainable software now. I've slung far smellier code before (I've got a BA in English), and besides, this way I get to perfect my svn diff skills.
Thanks again y'all,
Tim
On Mon, May 18, 2009 at 2:40 PM, Fred Jones
<fredthejonester@...> wrote:
> and one monster custom module (~ 7000 lines), and I'm looking at migrating
> to 6.x sometime in the next few months.
7K? Wow.
> So I was wondering if anyone had any suggestions on things to look out for
> or a generalized timeline? My guess was at least 100 hours to upgrade to
> 5.18, migrate to 6.12, test the system, and then adjust the theme and api
> calls.
It's a very tough call when you consider that you have 7K lines of
code that you aren't familiar with it. One note I can share is that
you definitely must examine each contrib module's upgrade
instructions--many *require* that you first upgrade them to the
latest/last 5.x version before moving to 6. And they mean it. ;)
Good luck.
--
Tim Loudon
t: 781.686.6096
e:
tloud365@...
