Now that three months have passed since the release of RubyGems 0.9.0, are folks upgrading to this new whizzy version? Well, as part of fixing this bug I've imported the past few months of RubyGem download data into the RubyForge database, and so now we've got some numbers. Yay!
Here are the downloads by client id since, more or less, the end of June:
gforge=> select client_signature, count(client_signature)
from gem_downloads
group by client_signature
order by count(client_signature) desc;
client_signature | count
--------------------+--------
RubyGems/0.9.0 | 858543
RubyGems/0.8.11 | 661509
RubyGems/0.8.10 | 109686
RubyGems/0.8.3 | 3803
RubyGems/0.8.99.2 | 3236
RubyGems/0.8.4 | 1220
RubyGems/0.8.8 | 967
RubyGems/0.8.6 | 695
RubyGems/0.8.11.6 | 312
RubyGems/0.8.99.1 | 227
RubyGems/0.8.99 | 214
RubyGems/0.9.0.1 | 152
RubyGems/0.8.7 | 104
RubyGems/0.8.11.15 | 75
RubyGems/0.9.0.6 | 47
RubyGems/0.8.5 | 24
RubyGems/0.8.11.11 | 8
RubyGems/0.8.11.3 | 8
RubyGems/0.9.0.4 | 6
RubyGems/0.9.0.2 | 5
RubyGems/0.8.11.2 | 5
RubyGems/0.8.11.7 | 1
RubyGems/0.9.0.3 | 1
(23 rows)
So 0.9.x leads the way! This is great to see; the more folks that are using RubyGems 0.9.0, the easier the load on rubyforge.org will be thanks to Jim Weirich's optimizations to the gem indexing gizmo. Good times!