update changelog for 1.2.0
Version 1.2.0
fix whitespace test
Revert "Ruby 2.0 (trunk ruby) is not Ruby 1.9"

As discussed in #1539 and #2056, Bundler uses platforms to distinguish Ruby ABI versions. That means the known (and ATM supported) use cases for the ruby_19 platform include Ruby 2.0.

This reverts commit dcfb640c2c78671a90ab10ce4c8d98a157ad975c.
Merge branch '1-2-stable'
point to gembundler.com
point to gembundler.com
rake:release should guard against both uncommitted and unstaged changes
Catch Errno::ETIMEDOUT errors as well.
Merge pull request #2091 from jmoses/master

Catch Errno::ETIMEDOUT errors from Fetcher#fetch
test if no ruby version is specified for platform --ruby
Fix #2096. Definition#new use nil for ruby_version default value

Definition#validate_ruby! checks for nil and not an empty string
test to ensure bundle clean works when suing BUNDLE_WITHOUT groups
Revert "`clean` should not remove gems in the lockfile"

This reverts commit aefa530cdc7b209bc646e98b7a730078d064665f.

bundle clean should remove BUNDLE_WITHOUT gems. BUNDLE_WITHOUT settings
should be standardized across commands as well if you are using
BUNDLE_WITHOUT you probably don't want the gems to be around when
cleaning.
Default new gem's gemspec to have MIT license.

When creating a new gem, there is already an MIT license file added
(https://github.com/carlhuda/bundler/pull/1571), this makes it explicit
in the .gemspec so that tools like https://github.com/pivotal/licensefinder
can easily detect it.
have a timeout around the gemcutter API endpoint

The API endpoint can sometimes hang and not return a response but open a
connection. Bundler before would just hang for a long time. This adds a
reasonable timeout, since the point of the API is to speed up the
install process. If the API takes too long, we should fall back on
cloudfront and the modern index, since that will likely be faster.
update changelog for 1.2.1
use Net::HTTP's read_timeout setting instead

talked with @drbrain about net/http timeouts, and we decided it was
better than having to do a manual Timeout.
shut the server down in the test
use the API_TIMEOUT constant