Drupal 7's "maturity period" will be far shorter than it was for D6. Drupal 6 had a very long lag time while contrib caught up. For Drupal 7, we have Fields in core, tons of additional functionality in core, VIews is already usable on D7, there's hundreds of modules with stable or beta versions for D7...
My company (Palantir.net) has been building Drupal 7 sites for over six months now. If you know what you're doing, it's ready *today*. There are some significant contribs that arent ready, but that's a great opportunity for you to jump in and help get them ready. And the knowledge you gain in so doing is worth gold to clients looking for someone who can show they really know their Drupal.
Unless you need a specific module that's not already ready, and you have a tight deadline, Drupal 7 is already mature enough, I'd argue. Drupal 6 was an anomaly in that regard.
--Larry Garfield
On Monday, February 21, 2011 12:20:22 am Mutuku Ndeti wrote:
Hi,
I am using d6 for now until d7 is "mature" enough. This would be about 6 months to one year after launch.
All the best.
On 2/21/11, Warren Vail warren@vailtech.net wrote:
I host better than a dozen Drupal sites, and while I am planning to switch my dev site to D7 in about 6 mos, if that goes well, I'll begin to move my client sites when I discover the support for D7 (newer and better modules) is better than D6. I don't want to expose my clients to "The Bleeding Edge".
Warren Vail