<div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Sam Cohen wrote:<br>
> I've still got a couple of 4.7 sites that are serving nonprofit<br>
> clients very well and they are very happy with them. I'd like it if<br>
> they paid for an upgrade, but I can't imagine requiring them to do so.<br>
<br>
</div>By the way, I was ignorant of these issues when I set up my first two<br>
clients with Drupal. I now do their security updates for free, and if<br>
they haven't upgraded of their own accord by the time Drupal 5 is EOL, I<br>
will upgrade them to D6 for free. I consider the unpaid time the cost of<br>
my Drupal education. I offer my new clients a monthly maintenance plan<br>
to cover the cost of security updates. If they refuse it, and lack<br>
in-house expertise to apply the updates themselves, they do so fully<br>
educated about the risks they are taking.<br>
<font color="#888888"><br>
-Matt</font></blockquote></div><br>You sure make upgrading to Drupal 6 seem really easy. In my experience, f a site has a lot of customization or uses modules that haven't been ported -- or modules that simply work differently (views1 to views2) upgrading can take days -- even weeks. In many cases, doing it for free isn't even an option. <br>
<br>Sam<br>