<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>If I do those things I
hope to end up with sites that have very little customization. That doesn't eliminate upgrade problems, but it makes the upgrade much much more manageble.</blockquote><div><br>Yes, but then we're talking about simple sites. <br>
<br> I'm talking about big sites with lots of customization, where clients might spend well over 100k on customization. I'm just questioning whether those who build those sites are building in -- or being upfront -- about the cost of upgrading to D6 and then D7. <br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div class="im">2009/3/29 Sam Cohen <span dir="ltr"><<a href="mailto:sam@samcohen.com" target="_blank">sam@samcohen.com</a>></span><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I understand the logic in what you're saying, but it makes me wonder whether or not in the real world, big site developers who are now building complex sites in Drupal 6, with lots of customization, are building into their fees and being upfront with clients about what it's going to cost to upgrade that site to Drupal 7. <br>
<br></blockquote></div><br>
<br>_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br></blockquote></div><br>