[consulting] Drupal Primer Course

[Khalid B]

> > One more thing: should we bother with 4.6 vs. 4.7? Or just go 4.7
> > full speed? The downside here is that 4.6 may live on longer than
> > we would like to, and covering it would breath more life into it. On
> > the other hand ignoring it may not be realistic.
>
> This raises an interesting point. The success of Drupal over the past
> year will mean that there will be much more demaned for support of
> 4.6. In the context of a DrupalCamp type of lesson plan, 4.7 only
> makes sense -- after all, it's geared towards new development, new
> users, and/or new sites. But while 4.5 faded rather quickly, I
> suspect 4.6 will linger much more, and depending upon future upgrade
> paths, 4.7 could linger longer still beyond its own "expiration date."

The API changes between 4.5 and 4.6 were not that much compared
to the magnitude of 4.6 to 4.7.

Don't get me wrong, I wish 4.6 to fade away quickly too, and full momentum
to be behind 4.7 going forward.

I think by focusing new development and training efforts on 4.7 we will
give the message that this is the way going forward. The new "converts"
will only know 4.7 this way.

My fear, which may be exaggerated, is that 4.6 would continue to live
on for a long time due to inertia and customers having investments in
4.6 sites and not wanting to go thru the expense and trauma of moving
to it. This happened in other free software projects too, such as Apache
1.3 vs. Apache 2, or PHP 4.4 vs. PHP 5.x, ...etc.

Let the "market" drive it, but let us also try to nudge it.