Oh I know, I wasn't trying to blame either the module developers or Drupal itself. I've been hired by a big company to speed-develop a site, and initially they wanted Drupal 6, and I've had to convince them to go with D5.7, because I would need a hell of a lot of more time if I was to patch all the modules, we're gonna need for this project (which is a huge, high-profile deal).
So, I of course agree that patching would be the right way to go, but it's just not feasible with the time I have for this project.
thanks Morten
Everyone is busy, if you want it faster the correct thing to do is create a patch for the modules you need following the d5 to d6 conversion guide and submit them to the appropriate module issue queues. The d4.7 to d5 conversion still shows modules that have no love. You may need to be willing to take on a co-maintainer role or even a maintainer role following the guidelines set forth for doing so. See http://drupal.org/handbooks for the documentation for developing for Drupal.
If you wish to wait it may be at least 6 to 8 months before the modules you use are ready for "professional deployment".
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/