[consulting] Staying Current

[Victor Kane]

I agree with Benjamin and Sean.

Above and beyond total agreement with Karen and others in terms of what
developers per se can be expected to do (they cannot support infinite or
even > 2 versions), there is a growing demand for centralizing real world
expectations for Drupal 5.x backporting.

Where there is demand there are solutions.

Victor

On Sun, Mar 29, 2009 at 11:01 AM, Sean Burlington
<sean at practicalweb.co.uk>wrote:

> Benjamin Melançon wrote:
>
>> Agreed on the importance of staying current, but an upgrade is often
>> necessarily a redevelopment, which not all clients can afford.
>>
>> OpenFlows already maintains backports of security patches for Drupal
>> core and a few contrib modules used by the sites of behind-the-times
>> clients:
>>
>>
> ... and my expectation is that if the security team drop support for D5 (as
> planned) then we'll find other people working on big D5 projects
> contributing security fixes as well.
>
> This is potentially a really good way to get some of the companies
> benefiting from Drupal to contribute stuff back.
>
> I think D5 is too big to EOL
>
> especially as D6 hasn't been complete enough (still no stable e-commerce)
> for long enough (new D5 sites still being launched now)
>
>
> --
>
> Sean Burlington
>
> www.practicalweb.co.uk
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.drupal.org/pipermail/consulting/attachments/20090329/2c15ba8d/attachment-0001.htm>