cant_wait 0.0.3 → 0.0.4

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    OTVmY2I3NmViN2ZiZDJhNjZlNzExNzNlNmIxYTdkYmI2MTQ5NmY5MA==
+    YWJhMmUzZDZjYjBhMmVjN2FiZjk4YTdjNjcwMTY2ZTYyY2EyYzBjMQ==
   data.tar.gz: !binary |-
-    ODE0OWFkYmFiMTg3ZGYzMmEzZTIwY2JiNDRhMjk4NjY0Yzc2MWE1NA==
+    MmZmYzczMjRiZTRiN2I5NGRmMDhkNTZlODI5YTdmNDA1ZmRlNDYxMw==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    ZDM5NTE4N2ZkODQ3OWJlOTVhM2E4YTNmZjk1YTU4Njk5NjMzZTg3YjhmOGJl
-    MGQ0ZWQ1MzhkMjZkZTAzZWQ1MDVhMzg4ZGY5YzUzZjY2OGFhMzE5YjdiNzVm
-    NmRhOTVlYmNmYWQ0NDg5MDljYTg2YjJkNWM4ZmY1NzI2MDg3Y2M=
+    ZTIzNzc0MzA4Yzg4YTI5MGExNjJmNzE2OGYyOTg5OWJhZjJkMTQwNGY1YTM5
+    ODM5MWFjZjEyN2Y1NDUyZjRiMjRiM2E1MzcyMzEzNDk0YzE3NzUwNjYyNmM2
+    MTBjNmJjMjU4MzI3OTBlMzA3NmFhYjVlMGNmODYyZDg3NGYyNTA=
   data.tar.gz: !binary |-
-    YzkxZmExZTk1ZjJhNjJlNjkzMzVlZGEyODhhMGM0ODI2ZTBlM2E0YTg5YjRj
-    NzQzYjEzZTMwNTc1ODU3Njg2MTVlNjEzNWE4YTUzNjRkZGEzYWMwYzA4YWQ4
-    ZDlhNTlhOTYxZDVlNDlhNzgzNmNlN2JlYmNjYTVhOGU2NDU1MGE=
+    MTI2ZjIwNjRkNGY4YjU4YmNjODQ4ZmZhZjA4MWVkZjEwN2M4MzdkOTdlNjA2
+    YzdjMGY2Mjg4NjU5M2NhNTQ1MGUyNjM4N2FmYjUxNjY1ZjNkZGJjZDBkNGE0
+    NTExZmUxMDI1ODZhYzg0YzIzZGEyNWM2ODE0MDU1MTc0ZGM1YmE=

data/.gitignore

@@ -1,18 +1,6 @@
-*.gem
-*.rbc
-.bundle
-.config
 .DS_Store
-.yardoc
+*.gem
 Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
 pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
+test/test_apps/Test_*/log/*.log
+test/test_apps/Test_*/config/database.yml

data/.travis.yml

@@ -3,13 +3,13 @@ rvm:
   - 1.9.2
   - 1.9.3
   - 2.0.0
-  - jruby-19mode  # JRuby in 1.9 mode (last was 1.7.3)
-  - rbx-19mode    # Rubinius in 1.9 mode (last was 2.0.0, weekly build)
+  - jruby-19mode  # JRuby in 1.9 mode
+  - rbx-19mode    # Rubinius in 1.9 mode
 before_script:
-  # Before, Travis does a bundle install (cant_wait's Gemfile), installing the last version of Rails
+  # Before, Travis does a bundle install (cant_wait's Gemfile), which installs the last version of Rails
   - psql -c "CREATE ROLE tester WITH LOGIN PASSWORD 'secret';" -U postgres
   - psql -c 'CREATE DATABASE test WITH OWNER=tester;' -U postgres
-  # And here we remove Rails to allow its coexistence with others
-  - gem uninstall rails  # It used to be a singleton...
+  # We remove Rails to allow the installation of previous versions:
+  - gem uninstall rails
   - rake test:bundle
 script: rake test:run

data/CHANGELOG.md

@@ -23,3 +23,24 @@ Development:
 
   - Travis scripts stability fixes
   - Tests for Rails 4.0.0
+
+0.0.4 (August 15, 2013)
+=======================
+
+Features:
+
+  - Encoding UTF-8 (ruby 1.9)
+
+Documentation:
+
+  - Changes in the documentation
+  - Minimum ruby is MRI 1.9.1 or compatible
+  - Added a 'runtime dependencies' security advisory service.  A dynamic badge on the README files
+  - Added the code signing certificate, for gem signature verification
+
+Development:
+
+  - Streamlining PostgreSQL JDBC dependencies for JRuby
+  - Minor tweaks in the tests
+  - Tested with new patches of MRI for C Ruby 1.9.3 and 2.0.0
+  - Tests for Rails 3.2.14

data/README.md

@@ -1,9 +1,10 @@
 # cant_wait
 [![Gem Version](https://badge.fury.io/rb/cant_wait.png)](https://badge.fury.io/rb/cant_wait)
+[![Dependency Status](https://gemnasium.com/CarlosCD/cant_wait.png)](https://gemnasium.com/CarlosCD/cant_wait)
 [![Build Status](https://travis-ci.org/CarlosCD/cant_wait.png?branch=master)](https://travis-ci.org/CarlosCD/cant_wait)
 
 
-This Ruby gem allows to add a statement timeout for PostgreSQL databases within a Ruby on Rails application.
+This Ruby gem adds statement timeouts for PostgreSQL databases within a Ruby on Rails web application.
 
 From the PostgreSQL documentation:
 
@@ -22,11 +23,20 @@ From the PostgreSQL documentation:
 (Visit <http://www.postgresql.org/docs/devel/static/runtime-config-client.html> for more information)
 
 
-If any SQL statement takes more time than the timeout value (measured in milliseconds), its execution will be cancelled, and Active Record would raise a PGError exception.
+If any SQL statement takes more time than the timeout value (measured in milliseconds), its execution will be cancelled, and Active Record would raise an exception.
 
     ActiveRecord::StatementInvalid: PGError: ERROR:  canceling statement due to statement timeout
 
-If you find any problems, please feel free to open an issue in the gem repository ([GitHub](https://github.com/CarlosCD/cant_wait)).
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'cant_wait', '~> 0.0.4'
+
+And then execute:
+
+    bundle
 
 
 ## Usage
@@ -41,22 +51,14 @@ In the file <tt>config/database.yml</tt> of the Rails application, indicate a ti
 Then restart the application to establish the new database settings.
 
 
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'cant_wait', '~> 0.0.3'
-
-And then execute:
-
-    $ bundle
+## Dependencies
 
+The minimum requirement is Rails 3.0.3 and ruby.  The gem has been tested with Rails 3.0.3 and above (including version 4.0.0).  Previous versions of Rails are not compatible with the present version of bundler.
 
-## Dependencies
+The minimum version of ruby is MRI 1.9.1 or compatible, as the gem uses 1.9 syntax.
 
-Previous versions of Rails are not compatible with the last version of bundler, so the minimum requirement is Rails 3.0.3.
+It has also been tested with PostgreSQL versions 8 and 9, but it may work also in other versions supported by Active Record (see PostgreSQL documentation).
 
-The gem has been tested with Rails 3.0.3 and above (including version 4.0.0).  It has also been tested with PostgreSQL versions 8 and 9, but it may work also in other versions supported by Active Record (see PostgreSQL documentation).
 
 ### Supported Rubies
 
@@ -68,23 +70,27 @@ The gem has been tested with Rails 3.0.3 and above (including version 4.0.0).  I
 - jruby
 - Rubinius
 
-The gem may work just fine with a Ruby flavors/versions not listed above.
+The gem may work fine with other Ruby flavors/versions not listed above.
+
+See the development documentation below for more details.
+
+
+## Signature
+
+All the versions of **cant_wait** released from rubygems.org have been digitally signed.
 
-See the development documentation for more details.
+To verify that the gem has not been tampered with, I am providing the certificate used in its repository, at [Github](https://github.com/CarlosCD/cant_wait).
 
 
-## Development / Contributing
+## Development
 
-* Source hosted on [GitHub](https://github.com/CarlosCD/cant_wait)
-* Details on the test setup are in the file README.md within the test folder.  It includes details on testing in several Ruby and Rails versions.
+If you find any problem, please feel free to open an issue at the gem's repository ([GitHub](https://github.com/CarlosCD/cant_wait)).
 
-Contributing:
+These files could be of particular interest:
 
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
++ [The Change Log](https://github.com/CarlosCD/cant_wait/blob/master/CHANGELOG.md)
++ [Test setup details](https://github.com/CarlosCD/cant_wait/blob/master/test/README.md)
++ [Gem signature verification](https://github.com/CarlosCD/cant_wait/blob/master/cert/README.md)
 
 
 ## License
@@ -92,4 +98,4 @@ Contributing:
 **cant_wait** is released under the [MIT License](http://opensource.org/licenses/MIT).
 
 
-June 2013
+August 2013

data/cant_wait.gemspec

@@ -4,9 +4,11 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 require 'cant_wait/version'
 
 Gem::Specification.new do |spec|
-  spec.name          = 'cant_wait'
-  spec.version       = CantWait::VERSION
-  spec.platform      = Gem::Platform::RUBY
+  spec.name                  = 'cant_wait'
+  spec.version               = CantWait::VERSION
+  spec.platform              = Gem::Platform::RUBY
+  spec.required_ruby_version = '>= 1.9.1'
+
   spec.summary       = 'Complements the Ruby on Rails web application framework by providing statement timeouts for PostgreSQL databases.'
   spec.description   = 'Provides statement timeouts for PostgreSQL databases in a Ruby on Rails web application. Stops any SQL statement ' <<
                        'that takes more than a specified number of milliseconds.'
@@ -22,16 +24,14 @@ Gem::Specification.new do |spec|
 
   spec.add_dependency 'rails', '>= 3.0.3'
 
-  spec.signing_key = '/users/CarlosCD/.ssh/private_key.pem'
-  spec.cert_chain  = ['/users/CarlosCD/.ssh/public_cert.pem']
+  spec.cert_chain  = ['cert/public_cert.pem']
+  spec.signing_key = '/users/CarlosCD/.ssh/keys.pem' if $0 =~ /gem\z/
 
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.add_development_dependency 'bundler', '~> 1.3'
   spec.add_development_dependency 'rake', '~> 10.0'
   if RUBY_ENGINE == 'jruby' && RUBY_PLATFORM == 'java'
-    spec.add_development_dependency 'activerecord-jdbc-adapter', '~> 1.2'
     spec.add_development_dependency 'activerecord-jdbcpostgresql-adapter', '~> 1.2'
-    spec.add_development_dependency 'jdbc-postgres', '~> 9'
   else
     spec.add_development_dependency 'pg', '~> 0'
   end

data/cert/README.md

@@ -0,0 +1,70 @@
+# cant_wait ~ Gem Signature verification
+[![Gem Version](https://badge.fury.io/rb/cant_wait.png)](https://badge.fury.io/rb/cant_wait)
+[![Dependency Status](https://gemnasium.com/CarlosCD/cant_wait.png)](https://gemnasium.com/CarlosCD/cant_wait)
+
+
+All the versions of **cant_wait** released from rubygems.org have been digitally signed.
+
+To verify that the gem has not been tampered with, I am providing here the self-signed certificate used, which includes the public key.
+
+Therefore, you have now two pieces of information from two different sources:
+
+- The signed gem from [RubyGems.org](http://rubygems.org/gems/cant_wait)
+- The certificate from [Github.com's](https://github.com/CarlosCD/cant_wait) repository
+
+This mechanism is far from perfect, but I believe it is better than no security at all, until the Ruby community and RuybyGems.org agrees in something better (and free).
+
+
+## Cryptographic signature verification
+
+To verify the gem's signature:
+
+1. First install the certificate public_cert.pem downloaded from the cert folder of Github's repository (master branch):
+
+        gem cert -a public_cert.pem
+
+2. Then Download the last version of the gem (or a version you intend to use) from rubygems.org.  The file would look something like:
+
+        cant_wait-X.Y.Z.gem
+
+   Where <tt>X.Y.Z</tt> is the gem's version.
+
+3. Next the gem can be installed with the high security option, which checks that the gem is signed and the signature matches an installed certificate:
+
+        gem install cant_wait-X.Y.Z.gem -P HighSecurity
+
+If the certificate or the gem has been tampered with, the gem command (RubyGems) should refuse to install it.
+
+
+## On certificate renewal and expiration
+
+The certificate used to sign **cant_wait** versions 0.0.1 to 0.0.3 had a short validity time, so the one provided in the cert folder in Github is a renewal of the original, with a longer expiration date. I've used this certificate from versions 0.0.4 and on.  However, the verification process explained above won't complain, as both certificates use the same cryptographic keys and same identity data.
+
+The reason for this notice is that other verification systems may say that the certificate doesn't match for early version of the gem, even if the public key is the same.
+
+
+## Use of Bundler to install signed and trusted gems, or not
+
+The usual way to install gem dependencies using bundler, as it is commonly done in Rails, is by executing the command:
+
+    bundler
+
+or
+
+    bundler install
+
+If used this way, unless additional parameters are added by your particular setup (maybe using bundle's config), bundler doesn't verify gem signatures.  If this is a concern to you, then you should:
+
+1. Install the certificates of the gems you know and trust, as explained above (<tt>gem cert -a certificate</tt>).
+2. Bundle install with the <tt>High security</tt> option:
+
+        bundle --trust-policy HighSecurity
+
+    or
+
+        bundle install --trust-policy HighSecurity
+
+Please be aware that the practice of signing gems is not followed as a standard by the whole development community, so you may find that many of the most popular ruby gems are not signed (bundler and rails are not signed at this moment).  Therefore you may need to think about it, compromise, or carefully audit the code of the gems you try to install.
+
+
+August 2013

data/cert/public_cert.pem

@@ -0,0 +1,21 @@
+-----BEGIN CERTIFICATE-----
+MIIDezCCAmOgAwIBAgIJAPqnpDrIxB5EMA0GCSqGSIb3DQEBBQUAMFMxCzAJBgNV
+BAYTAlVTMQswCQYDVQQIDAJNRDERMA8GA1UEAwwIQ2FybG9zQ0QxJDAiBgkqhkiG
+9w0BCQEWFWNjYXJyb2R1cGxhQGdtYWlsLmNvbTAgFw0xMzA3MTgxOTMwNDJaGA8y
+MDUzMDcwODE5MzA0MlowUzELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAk1EMREwDwYD
+VQQDDAhDYXJsb3NDRDEkMCIGCSqGSIb3DQEJARYVY2NhcnJvZHVwbGFAZ21haWwu
+Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx3/EdvkPDke6ifYd
+9GYENKzUG8tZTpWz2896PjggqDkegizOHENcF2ESUEyopxRP34/LrId/u3ZOhiM5
+yqjd8OvWVFcozpbY60d3HxnVwEfHlFf0ghXqCs2rY5XzY5viPyQ+vFX0v9U04vkZ
+P2cayJTMfuhdeH/3DwKqkHLzH+hM6rUOjY4RN0r0OWPhs2vNMujhjHWKI/j5gjYD
+q7l8og7yKmZlMYKYUrGguMZlTww61T8G0yoKbLLzXMJADUq3xwzbUM98mvePGsix
+FOgz2CNN7gBCkhqZyrcJVinn76IrHXHA2xHuNjK2Xfm1dFAqes2DeH9+0m4CiYNV
+aOaENQIDAQABo1AwTjAdBgNVHQ4EFgQUkYnGK6rP0uytzVtmxO6OrKST2AcwHwYD
+VR0jBBgwFoAUkYnGK6rP0uytzVtmxO6OrKST2AcwDAYDVR0TBAUwAwEB/zANBgkq
+hkiG9w0BAQUFAAOCAQEAMbe3ei8af8r2wvb6FQ/f/GlnFJfaPJIaDEj8emg2sSIg
+m7Qg3e601m1UF0hqTEGcjUmrrPrknOYv+JgwdBslBJnLasCADZshX2MIzjlzHG3W
+2tFGKGm3xaJbKbFJ3K1HWof399E9ecS02ZBErvoJvYjKBOV+DvYW18zryX/oMQGr
+3btYo3NlDuNXVpX5ChPC/QcvK3DLMP102YguZMjawympptozRHgvQYLNjmsZpi7+
+4Lx7TwZB/AT4xQfhKewXYTfvjRQRUKhnnhPh+CYwpl0xV9jun/8HHCVLWFyDLKa0
+j8swKkWECMke3qZmvKW8NTWQc4ffpbGtugif0Iw9bA==
+-----END CERTIFICATE-----

data/lib/cant_wait.rb

@@ -1,3 +1,5 @@
+# encoding: utf-8
+
 begin
   require 'cant_wait/version'
   require 'cant_wait/cant_wait_railtie' if defined? Rails

data/lib/cant_wait/cant_wait_railtie.rb

@@ -1,3 +1,5 @@
+# encoding: utf-8
+
 module CantWait
 
   ##

data/lib/cant_wait/version.rb

@@ -1,3 +1,5 @@
+# encoding: utf-8
+
 module CantWait
-  VERSION = '0.0.3'
+  VERSION = '0.0.4'
 end

data/tasks/testing.rake

@@ -9,7 +9,7 @@ namespace :test do
   TEST_RAILS_APP = [{ version: '3.0.3',  rails_root: 'test/test_apps/Test_3_0_03'},
                     { version: '3.0.20', rails_root: 'test/test_apps/Test_3_0_20'},
                     { version: '3.1.12', rails_root: 'test/test_apps/Test_3_1_12'},
-                    { version: '3.2.13', rails_root: 'test/test_apps/Test_3_2_13'},
+                    { version: '3.2.14', rails_root: 'test/test_apps/Test_3_2_14'},
                     { version: '4.0.0',  rails_root: 'test/test_apps/Test_4_0_0' }]
 
 
@@ -107,7 +107,7 @@ namespace :test do
       puts '============================================================'
       print '  rvm setting (if rvm is being used): '
       system 'rvm current'
-      puts "  Gem's ENV['BUNDLE_GEMFILE']='#{ENV['BUNDLE_GEMFILE']}'" if verbose
+      puts "  Gem's ENV['BUNDLE_GEMFILE']='#{ENV['BUNDLE_GEMFILE']}'"
     end
     can_wait_bundle_gemfile = ENV['BUNDLE_GEMFILE']
     initial_directory = FileUtils.pwd

data/test/README.md

@@ -1,25 +1,26 @@
 # cant_wait ~ development and test
 [![Gem Version](https://badge.fury.io/rb/cant_wait.png)](https://badge.fury.io/rb/cant_wait)
+[![Dependency Status](https://gemnasium.com/CarlosCD/cant_wait.png)](https://gemnasium.com/CarlosCD/cant_wait)
 
 
 ## Test setup and choices
 
 - Minitest, to keep things simple.
 - PostgreSQL database server (localhost or not).
-- I used rvm (not a need if other ruby version manager is preferred). 
+- I used RVM.  This is not a requirement, other ruby version managers should work as well.
 
 
 ## Test strategy: different Rails apps with random timeouts
 
 ### The problem
 
-The approach of using minimal Rails components (ActiveRecord, Railties) is problematic due to the amount of code that Rails loads and of how it changes in the default Ruby behavior.  I opted here to test the same way an end user would use the gem.
+The approach of using minimal Rails components (ActiveRecord, Railties) is problematic due to the amount of code Rails loads and of how it changes Ruby's standard behavior.  I wanted to test it as close as possible to how an end user would use the gem.
 
-To test in different Rails versions requires running several Rails Apps either simultaneously or sequentially.  Even if it is done in different threads, being a Rails App a singleton, it will result in:
+To test different versions of Rails, and different timeout scenarios, requires to run several Rails apps either simultaneously or sequentially.  Even using different threads, being a Rails Application a singleton, it will end up in:
 
     RuntimeError: You cannot have more than one Rails::Application
 
-This path also would make the test cases too distant to the real conditions you may encounter in isolated Rails applications, and even if the singleton restriction is removed, it will still apply to old versions of Rails.
+This path would also make the test cases too distant to the real conditions of an isolated Rails app.  Even if the singleton restriction is removed in the future (see this interesting discussion regarding Rails 4.1: <https://github.com/rails/rails/pull/9655>), it will still apply to older versions of Rails.
 
 ### A solution
 
@@ -30,9 +31,7 @@ I created 5 simple Rails apps, of different versions, in the folder test/test_ap
 Then I modified their Gemfile by adding gems for PostgreSQL, Minitest and Growl:
 
     if RUBY_ENGINE == 'jruby' && RUBY_PLATFORM == 'java'
-      gem 'activerecord-jdbc-adapter', '~> 1.2'
       gem 'activerecord-jdbcpostgresql-adapter', '~> 1.2'
-      gem 'jdbc-postgres', '~> 9'
     else
       gem 'pg', '~> 0'
     end
@@ -46,19 +45,19 @@ Then I modified their Gemfile by adding gems for PostgreSQL, Minitest and Growl:
 
     gem 'cant_wait', path: File.expand_path('../../../..', __FILE__)
 
-The rails apps require bundle install, specially when changing the version of Ruby to be used. To make it easier, I added a rake task (<tt>rake test:bundle</tt>).
+The rails apps require also to run <tt>bundle install</tt> for each app, especially when changing the version of Ruby used.  To make it easier, I added a rake task (<tt>rake test:bundle</tt>).
 
-The test is run through the <tt>rake test:run command</tt>.  The test goes over each rails app in sequence and:
+The actual test is run through the <tt>rake test:run</tt> command.  It goes over each Rails app in sequence and:
 
-1. It sets Bundle to use the test app's Gemfile
+1. It sets Bundler to use the test app's Gemfile
 2. It creates the app's <tt>config/database.yml</tt> with a random timeout
 3. It starts Rails
 4. It checks the version of Rails and ActiveRecord running.
 5. It checks that the PostgreSQL connection's statement_timeout is the expected.
 
-Due to the complex setup needed, I choose not to use the rake default to run the test, just to signal the tester to stop to consider these choices.
+Due to the complex setup, and to signal the developer to stop and consider these choices, I chose not to use the rake default to run the tests, as it is most common.
 
-And additional <tt>rake test:all</tt> will do both the bundle install and run the tests. This is the way travis-ci is set to run.
+An additional task <tt>rake test:all</tt> will do both the <tt>bundle install</tt> and run the tests.  Travis-ci also runs each of these tasks in sequence.
 
 
 ## The Testing process in detail
@@ -78,19 +77,20 @@ After cloning the gem, you can start testing it by following these steps:
 
 4. Set up your PostgreSQL test database and edit accordingly the file <tt>test/database.yml</tt>
 
-5. Get the Rails gems used by the test rails apps included:
+5. Get the gems used by the test Rails apps:
 
         rake test:bundle
 
-6. You are now done setting all up.  To run the tests:
+6. Your setup is complete.  To run the tests:
 
         rake test:run
 
-If so wanted, run the tests several times.  The tests use different random timeout scenarios, so each run may be a bit different.
+If desired, run the tests several times.  The tests use different random timeout scenarios, so each run may be a bit different.
+
 
 ## Travis
 
-I added travis-ci.org to check every build, as well as a badge to check the status last commit.
+I added travis-ci.org to check every build pushed to Github, and a clickable badge to check the status of the last test.
 
 Check the .travis.yml file for details.
 
@@ -99,24 +99,43 @@ Check the .travis.yml file for details.
 
 * Versions of Ruby:
 
-        1.9.2-p320       (MRI's last patchlevel of 1.9.2)  Linux and MacOS X
-        1.9.3-p327       (MRI)                             Linux
-        1.9.3-p429       (MRI last patchlevel of 1.9.3)    MacOS X
-        2.0.0-p0         (MRI)                             Linux
-        2.0.0-p195       (MRI last patchlevel of 2.0.0)    MacOS X
-        jruby 1.7.3      (java 1.7.0_15)                   Linux
-        jruby 1.7.4      (java 1.6.0_45)                   MacOS X
-        Rubinius 2.0.0   (1.9.3, 2013-06-12 JI)            Linux
+        1.9.2-p320          (MRI's last patchlevel of 1.9.2)  Linux and MacOS X
+        1.9.3-p327          (MRI)                             Linux
+        1.9.3-p429          (MRI)                             Linux and MacOS X
+        1.9.3-p448          (MRI last patchlevel of 1.9.3)    Linux and Mac OS X
+        2.0.0-p0            (MRI)                             Linux
+        2.0.0-p195          (MRI)                             Linux and MacOS X
+        2.0.0-p247          (MRI last patchlevel of 2.0.0)    Linux and Mac OS X
+        jruby 1.7.3         (Java 1.7.0_15)                   Linux
+        jruby 1.7.4         (Java 1.6.0_45)                   MacOS X
+        jruby 1.7.4         (Java 1.7.0_21)                   Linux
+        Rubinius 2.0.0.w30  (1.9.3)                           Linux
+
+  It requires at least MRI 1.9.1 or compatible.
 
 * Versions of Rails:
 
         Rails 3.0.3      First version using Bundler 1.3.5 (incompatible with Bundler 1.0.X)
         Rails 3.0.20     Last patchlevel of Rails 3.0 (at this moment)
         Rails 3.1.12     Last patchlevel of Rails 3.1
-        Rails 3.2.13     Last patchlevel of Rails 3.2 (many security fixes, last stable version)
+        Rails 3.2.13
+        Rails 3.2.14     Last patchlevel of Rails 3.2 (many security fixes, last stable version)
         Rails 4.0.0      Last Release of Rails 4.0
 
 * PostgreSQL versions 8.3.6 and 9.2.4.
 
 
-June 2013
+## Development / Contributing
+
+If you find any problem, please feel free to open an 'issue' at [GitHub](https://github.com/CarlosCD/cant_wait).
+
+Contributing:
+
+1. Fork it
+2. Create your feature branch (<tt>git checkout -b my-new-feature</tt>)
+3. Commit your changes (<tt>git commit -am "Add some feature"</tt>)
+4. Push to the branch (<tt>git push origin my-new-feature</tt>)
+5. Create new Pull Request
+
+
+August 2013