On Wed, Nov 5, 2008 at 8:51 PM, Chris Johnson <span dir="ltr"></span> wrote:<br><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;">
On Wed, Nov 5, 2008 at 10:01 AM, Nathaniel Catchpole<br>
<div class="Ih2E3d"><br>
> Exactly, and we're talking about core patches. Most active contrib<br>
> development is happening in Drupal 6, I generally don't see many patches<br>
> posted for Drupal 4.7 versions of contrib modules, or even Drupal 5<br>
> depending on which module it is.<br>
<br>
<br>
</div>We were? (talking about core patches?)<br>
<br>
I don't see that in this thread. We were talking about all patches,<br>
as far as I could tell.<br>
<br>
The arguments are indeed very different for core and contrib.<br>
<br></blockquote></div>Oh I see! Well I think the argument stands for contrib in a lot of cases, except that the release cycles are so much shorter (usually) that the most recent release is likely to be much closer to what you're actually using. Since very, very few contrib modules have D7 compatible versions that issue comes up a lot less, and in those cases, you'd probably want to forward-port patches until at least Beta/RC stage for the associated core release. So maybe we agree after all. Of course this all depends on the individual module, and individual maintainer.<br>
<br>Nat<br>