Release Candidate should mean feature freeze

Trevor,

I'll only speak to bundler here. We released an RC build of bundler when we honestly felt like there were no more showstopper bugs, and it felt plausible to release. There were a couple of features (like the --production flag), that we planned to add in 1.1. After doing so, we got a torrent of people who used bundler for the first time and were extremely confused by certain flags (like --disable-shared-gems).

Specifically, the correct practices for deploying bundler are somewhat different than using it in development, and it takes a few (documented) flags to get it working smoothly on deploy. Because of the amount of bug reports we received that could be resolved by providing a clearer default path on deployment, we took the plunge and added the feature.

Specifically with regard to --disable-shared-gems, the option was mostly an internal option that switched off using locally installed gems as a source during installation time, but the name implied that it resulted in complete isolation. People, for instance, were doing bundle install --disable-shared-gems and expecting it to result in isolation, when it was actually a nonsense incantation that was just causing pain.

When we looked at all the uses, we realized that people either install to their system (and therefore don't care about isolation) or are installing to a local directory (and therefore do care about isolation). We removed the option, clearly warning users who are still using it that it can be safely removed.