[consulting] Planning for future versions

[Victor Kane]

We are going with the best of both worlds, even for philo-Drupal 6 sites
(involving heavy use of i18n, for example).

That means: we are developing and launching everything in Drupal 5.x, and we
are offering a free upgrade to Drupal 6.x to all clients.

This was prompted by some clients pouting about Drupal changing all the time
(not true) and unwilling in general to put up with version specific
dependencies (don't blame them).

So since we don't tend to use anything but tier-1 modules, and tend to use
them heavily, 90% of the work will affect most customers. This is especially
true since we base most of our themes on Zen or other standard-based themes.

Since we have to do it anyway, and don't want to have to maintain different
sites with different versions, this will be an across the board upgrade,
which we will put off until "tier-1" modules (cck, views, i18n) are
production ready.

And if all of us did this, we could share solutions, difficulties, etc, I
think that would be great for the community.

Makes everyone happy.

Victor Kane
http://awebfactory.com.ar
"Free upgrade to Drupal 6"

On 8/16/07, Larry Garfield <larry at garfieldtech.com> wrote:
>
>
> A query for the other site builders out there.
>
> Drupal 6 is not yet in beta, but based on the past few versions my own
> prediction for its release is "sometime this fall".  No, this is not a "when
> will Drupal 6 be released?" email. :-)
>
> However, we have sites that are in planning that are also "sometime this
> fall".  That leaves an open question as to whether we plan to build on 5 or
> on 6.  (Some could be built in either, others are really better built in 6
> due to its new features.)  It's not just core, either.  Even after 6.0 is
> tagged, there's still the tier-1 modules (CCK, Views, etc.) that need to be
> finished (could be ready at the same time, could not), and tier-2 or tier-3
> modules that may be updated immediately or months later.  Naturally "if you
> need it, upgrade it and submit a patch", but that's time we'd need to factor
> in to our schedule if we're going to do so.  (And for some modules, I know
> I'd rather just let merlin do it because he's way more awesome than I am in
> that regard and could do it faster and better than I could. :-) )
>
> So, question for the audience.  How do you manage your future-plans,
> version-wise?  For sites that you have in the pipeline launching "sometime
> this fall", or "early next year" or whatnot, are you looking toward a Drupal
> 5 site?  Drupal 5 that gets quickly upgraded (at extra
> expense/refactoring)?  Drupal 5 that skips 6 and eventually upgrades
> straight to 7 (and therefore doesn't get a lot of the new D6-generation
> modules)?  Wait for 6?  Build on a 6-RC and track head, and hope the major
> modules are keeping up?
>
> What's your future-resistant strategy for this point in the development
> cycle?
>
> --Larry Garfield
>
> _______________________________________________
> 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/20070816/71c91b02/attachment.htm