<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jun 2, 2006, at 8:45 AM, John Handelaar wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Probably the easiest way to "patch" is to get 4.7.2 </FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">and overwrite everything.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>I recommended that Drupal 4.7 ship with a Patches directory. In interviews with administrators we found that it was taking from 20 hours to 40 hours to upgrade Drupal when you factored in absolutely everything including feature requests, testing, user training etc. One of the reasons was that so many people had patched Drupal.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>By adding a patches directory we encourage people running Drupal sites to keep a set of patches that most likely apply against security releases easily. If we did add a patches directory it would make it easier to recommend what John is suggesting.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Kieran</DIV></BODY></HTML>