<div class="gmail_quote">On Sun, Mar 29, 2009 at 1:53 PM, Sean Burlington <span dir="ltr"><<a href="mailto:sean@practicalweb.co.uk">sean@practicalweb.co.uk</a>></span> wrote:<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">Alex Urevick-Ackelsberg wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And how much of that code have you released into the wild? It strikes<br>
me that your problem may be, well, your problem. It's not up to me to<br>
</blockquote>
<br></div>
</blockquote><div><br>OK guys, gentle, gentle, we're just discussing this here, no-one's telling anyone what to do. <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Despite the apparent reluctance of the Drupal establishment to accept this.<br><font color="#888888">
</font></blockquote><div><br>I don't believe there is a reluctance to accept this.<br><br>I think Karen explained the situation very well.<br></div></div><br>Whereas I agree with your position that backports need to be considered (and so those of us that do should band together and work on that), you can't blame developers for having a developer-centric view of things.<br>
Karen explained: no-one can maintain more than two releases of a module they are maintaining...<br>It's a question of resources.<br><br><br>