[consulting] preparing clients for Drupal 5 obsolesence

[George]

yeah, the drupal core devs learnt that lesson the hard way, and are 
making unstable releases to allow module devlopers to get their hands on 
the code and start updating their modules before the final release.

so, with the modules being developed a lot faster for 7, and depending 
on when it's out, and on how complicated the site is, 5-7 may well be 
possible in some cases if you're brave!

Brian Vuyk wrote:
> I'll sign on to this. Last time around, I had many clients who wanted 
> sites built on D6. It doesn't look good to have to explain that while 
> the shiny new toy has been released, you have to wait for a few months 
> before you can play with it in a serious way.
>
> In the D5-D6 transition, I think a lot of modules were held up because 
> of Views & CCK. Many modules integrate with these two, and so until they 
> were ported in relatively final form, porting could not proceed up the 
> chain. Will we see the same this time around? During the D5->D6  
> transition, Views as well as a few other higher-profile modules went 
> through a major rewrite as well as porting. I don't believe the same is 
> true this time around. This should reduce the time for modules back up 
> the chain to port over.
>
> Brian
>
>
>
> Matt Chapman wrote:
>   
>> If we all refuse to invest any 
>> more labor in Drupal 5, even if it is faster or easier to do so, we can 
>> instead focus our energies (and our clients' funding) on porting and 
>> extending Drupal 6 & 7 modules now, and we won't have to relive the 9 
>> month lag between the release of a new Core and it's viability for real 
>> projects.
>>     
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>