For me I use a diff tool to trace the changes. I also join the cvs mailing list to trace changes in codes.
For me, I just keep a txt file list. I record the hack/plugin name, the page the code is change on and where it is located, the approx line number where the code is going to be, the original code, and what it is changed to.
I also keep all my main pages, in a separate folder on my computer. I have a folder for my site things, in that I have a PHP pages folder where I store my index, css, archives, comments and other related pages. That way, when I have to work on them, they are all right there.
Works well for me at least. LOL
I make a ‘mod-list’ (planning on doing one today actually!) which, so I don’t lose it, I post to my blog.
Once I’ve upgraded, I work through the list.
I don’t mind this, as it gives me the chance to evaluate just how much I may use a feature and if I decide I don’t want, leaving it out is maybe easier than having to remove it from the code (hack / plugin dependent of course).
I also backup my files regularly, esp the index and css when I have fiddled about even more …
Another thought …… or two.
Before someone upgrades, they really should be asking themselves WHY (unless you are not at 1.2mingus yet !).
If the feature list adds little or nothing to the functionality that you actually want, then why bother ? 1.2 has pretty much all I want in it, so unless 1.3 offers something great that I had not considered but find useful (I’ll run 1.3 on a testblog) then I’ll stick with 1.2
The other thing is that the more you customise your blog, the more you make everything work and look the way you want it to, the more work you are making for yourself when it comes to an upgrade. If you want (see above) the latest features, but you had not modified any files, then upgrading is a doddle.
But if you have spent (invested) time in creating a certain ‘look’ and feature-set, then you will have to do the same again – only this time it will be quicker as you know what you are doing.
