README.md in gems-0.3.0 vs README.md in gems-0.4.0
- old
+ new
@@ -10,11 +10,11 @@
-------------
[http://rdoc.info/gems/gems](http://rdoc.info/gems/gems)
Continuous Integration
----------------------
-[](http://travis-ci.org/sferik/gems)
+[](http://travis-ci.org/rubygems/gems)
Usage Examples
--------------
require 'rubygems'
require 'gems'
@@ -26,10 +26,15 @@
puts Gems.search 'cucumber'
# Returns an array of version details for coulda.
puts Gems.versions 'coulda'
+ # Returns the total number of downloads for rails_admin 0.0.0.
+ # Defaults to the latest version if no version is specified.
+ # Defaults to RubyGems.org if no gem name is specified.
+ puts Gems.downloads 'rails_admin', '0.0.0'
+
# Returns the number of downloads by day for coulda 0.6.3 for the past 90 days.
# Defaults to the latest version if no version is specified.
puts Gems.downloads 'coulda', '0.6.3'
# Returns the number of downloads by day for coulda 0.6.3 for the past year.
@@ -98,16 +103,16 @@
* by suggesting new features
* by writing or editing documentation
* by writing specifications
* by writing code (**no patch is too small**: fix typos, add comments, clean up inconsistent whitespace)
* by refactoring code
-* by closing [issues](https://github.com/sferik/gems/issues)
+* by closing [issues](https://github.com/rubygems/gems/issues)
* by reviewing patches
Submitting an Issue
-------------------
-We use the [GitHub issue tracker](https://github.com/sferik/gems/issues) to track bugs and
+We use the [GitHub issue tracker](https://github.com/rubygems/gems/issues) to track bugs and
features. Before submitting a bug report or feature request, check to make sure it hasn't already
been submitted. You can indicate support for an existing issuse by voting it up. When submitting a
bug report, please include a [Gist](https://gist.github.com/) that includes a stack trace and any
details that may be necessary to reproduce the bug, including your gem version, Ruby version, and
operating system. Ideally, a bug report should include a pull request with failing specs.
@@ -122,9 +127,32 @@
6. Add specs for your feature or bug fix.
7. Run <tt>bundle exec rake spec</tt>. If your changes are not 100% covered, go back to step 6.
8. Commit and push your changes.
9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
+Supported Rubies
+----------------
+This library aims to support and is [tested
+against](http://travis-ci.org/rubygems/gems) the following Ruby
+implementations:
+
+* Ruby 1.9.1
+* Ruby 1.9.2
+
+If something doesn't work on one of these interpreters, it should be considered
+a bug.
+
+This library may inadvertently work (or seem to work) on other Ruby
+implementations, however support will only be provided for the versions listed
+above.
+
+If you would like this library to support another Ruby version, you may
+volunteer to be a maintainer. Being a maintainer entails making sure all tests
+run and pass on that implementation. When something breaks on your
+implementation, you will be personally responsible for providing patches in a
+timely fashion. If critical issues for a particular implementation exist at the
+time of a major release, support for that Ruby version may be dropped.
+
Copyright
---------
Copyright (c) 2011 Erik Michaels-Ober.
-See [LICENSE](https://github.com/sferik/gems/blob/master/LICENSE.md) for details.
+See [LICENSE](https://github.com/rubygems/gems/blob/master/LICENSE.md) for details.