I don't have any problem warning people off of vB5, but it's not going to be especially effective if it's just on our word and if we ask no questions. Like, do we know if they've already bought a license? If we ask, and find out they have, then we should stress the importance of running this on a demo board on their same server and really testing and retesting that upgrade, in addition to finding out what modifications won't make the journey. If they haven't bought the upgrade yet, then we should point them to the demo site, and the vB.com forums/bug tracker. Find out what it is they want out of the software and then make recommendations, so they don't waste their money. Let them see what the issues are, and then let them make the final decision as to what they should do.
These are the same steps we'd take for any modification. Why not for the core script itself?
|