Rewrite all what's new pages from HAML to Markdown (#1051)

Signed-off-by: Takuya Noguchi <[email protected]>

source/v1.12/whats_new.html.md

@@ -0,0 +1,30 @@
+# What's New in v1.12
+
+### New index format
+
+Bundler now fetches gem metadata using [the new index format](https://andre.arko.net/2014/03/28/the-new-rubygems-index-format/) speeding up `install` significantly.
+In addition to the speed increases provided by the format itself, we’re also serving the new index directly from the Fastly CDN.
+That means Bundler will be able to talk to a server located nearby, no matter where you are in the world.
+We expect that to make a huge difference, especially in Oceania and Africa. 🎉
+
+### Outdated by version significance
+
+It is now possible to run `bundle outdated` with the flags `--major`, `--minor`, and `--patch`.
+Using those flags, you can limit Bundler to only show you new versions that are both allowed by your `Gemfile` and also meet the criteria of only changing the major, minor, or patch version of the gem.
+You can combine them to get only minor and patch updates, or even only major and patch updates (but I have no idea why you would want to do that)
+
+### Ruby version locking
+
+It is now possible to use regular gem version requirements, like `ruby "~> 2.3"`, in your `Gemfile`.
+Bundler will save your exact Ruby version (e.g. "2.3.1") into your `Gemfile.lock`.
+You can update the ruby version by running `bundle update --ruby`, and that will update the lock
+to match your current version of Ruby the same way Bundler currently updates gem versions.
+Bundler 1.12 also includes:
+
+- running `bundle exec` now about 0.25 seconds faster
+- support for Ruby 2.4
+- support for RubyGems 2.6.3
+- support for frozen string literals
+- many, many, many bugfixes
+
+<a href="https://github.com/rubygems/bundler/blob/1-12-stable/CHANGELOG.md" class="btn btn-primary">Full 1.12 changelog</a>

source/v1.13/whats_new.html.md

@@ -0,0 +1,49 @@
+# What's New in v1.13
+
+The [Bundler 1.13 announcement](/blog/2016/09/08/bundler-1-13.html)
+includes context and a more detailed explanation of the changes in this version. This is a summary of the biggest changes. As always, a detailed list of every change is provided in
+[the changelog](https://github.com/rubygems/bundler/blob/1-13-stable/CHANGELOG.md).
+
+### New `doctor` command
+
+Add the `doctor` command for automated troubleshooting. So far, it can automatically detect gems that have been compiled against libraries that no longer exist, and compile them again to fix them.
+(Thanks [@mistydemeo](https://github.com/mistydemeo)!)
+
+### Support for `required_ruby_version`
+
+Gems that declare a `required_ruby_version` will now resolve correctly as long as your Gemfile contains a `ruby` declaration.
+If a gem cannot be resolved because of your Ruby version, the error will correctly indicate that your Ruby version conflicts with your other gem version requirements.
+
+### Manage locked platforms
+
+In the past, the only way to resolve your Gemfile on a new platform (like `java` or `mswin`) was to run `bundle install` on that platform.
+We've added explicit options to the `lock` command to allow managing platforms.
+Platforms can be added using `bundle lock --add-platform NAME`, and platforms can be removed using `bundle lock --remove-platform NAME`.
+
+### Fine controls for the `update` command
+
+The `update` command now has several options to enable users to fine-tune exactly what it is that they will get,
+using the new flags `--major`, `--minor`, `--patch`, and `--strict`.
+It was also recently pointed out to us that running `update` could even result in some locked gems being changed to an older version!
+We can’t change the default behavior to avoid that until version 2.0, but for now we’ve added a config setting.
+To prevent the `update` command from ever “upgrading” you to an older version, run `bundle config only_update_to_newer_versions true`.
+
+### Experimental plugin system
+
+The plugin system also supports "source" plugins, which means it should be possible to use gems from Subversion, Mercurial, S3, or anything else you can think of.
+In addition to source plugins, we've started adding new "lifecycle" hooks.
+That means plugins will be able to hook in and run their own code before, during, or after the install or update process.
+
+### Experimental Bundler version locking
+
+automatically trampoline to the bundler version locked in the lockfile, only updating to the running version on `bundle update --bundler` (@segiddins)
+Bundler 1.13 also includes:
+
+- Support for RubyGems 2.6.4
+- Automatic gem installation for `bundler/inline`
+- Dramatic resolver optimizations
+- Better load-based `exec` command
+- Support for setting "mirror" servers by hostname
+- Automatic retrying for gem downloads
+
+<a href="https://github.com/rubygems/bundler/blob/1-13-stable/CHANGELOG.md" class="btn btn-primary">Full 1.13 changelog</a>

source/v1.14/whats_new.html.md

@@ -0,0 +1,36 @@
+# What's New in v1.14
+
+The [Bundler 1.14 announcement](/blog/2017/03/28/bundler-1-14-so-many-fixes.html)
+includes context and a more detailed explanation of the changes in this version. This is a summary of the biggest changes. As always, a detailed list of every change is provided in
+[the changelog](https://github.com/rubygems/bundler/blob/1-14-stable/CHANGELOG.md).
+
+### Conservative updates
+
+The conservative flag allows `bundle update --conservative GEM` to update the version of GEM,
+but prevents Bundler from updating the versions of any of the gems that GEM depends on,
+similar to changing a gem's version number in the Gemfile and then running `bundle install`.
+
+### Checksum validation
+
+As part of the compact index format provided by RubyGems.org, Bundler now has access to checksums for every .gem file.
+Starting with version 1.14, Bundler actively validates those checksums against downloaded .gem files before installing them. Hooray! 🎉
+
+### Improved platform support
+
+The `force_ruby_platform` and `specific_platform` settings tell Bundler to always compile gems and to consider platforms during dependency resolution, respectively.
+These options can significantly improve things for users installing a single bundle on more than one platform.
+
+### Required Ruby and RubyGems conflict messages
+
+If any gem conflicts with your Ruby or RubyGems version, the error message will now show both the conflicting dependencies and the chain of parent dependencies that led to the conflict.
+Bundler 1.14 also includes:
+
+- Installing gems using `sudo` will now always prompt for a password, even if the sudo password is cached from an earlier command
+- The Gemfile method `platform` now supports Ruby 2.5, allowing arguments like `:ruby_25` or `:mri_25`.
+- The “lockfile is missing dependencies” error (triggered by certain old lock files that were missing information) is no longer fatal. We now print instructions on how to repair the Gemfile, and install using one thread.
+- Running `require "bundler"` is now about five times faster than it used to be.
+- Bundler now works when run by users without a home directory.
+- The output from `bundle env` is now preformatted as Markdown for pasting into a GitHub issue.
+- After Bundler 2.0 is (eventually) released, Bundler 1.14 and greater will be able to automatically switch to Bundler 2.0+ for apps that need it.
+
+<a href="https://github.com/rubygems/bundler/blob/1-14-stable/CHANGELOG.md" class="btn btn-primary">Full 1.14 changelog</a>

source/v1.15/whats_new.html.md

@@ -0,0 +1,21 @@
+# What's New in v1.15
+
+The [Bundler 1.15 announcement](/blog/2017/05/19/bundler-1-15-bundle-oh-so-fast.html)
+includes context and a more detailed explanation of the changes in this version. This is a summary of the biggest changes. As always, a detailed list of every change is provided in
+[the changelog](https://github.com/rubygems/bundler/blob/1-15-stable/CHANGELOG.md).
+
+### Exec optimization
+
+We've made `bundle exec` faster by reducing the impact of each additional gem in your application. In applications with hundreds of gems, this change made `exec` half a second (!) faster.
+
+### `bundle issue`
+
+The `issue` command provides troubleshooting help. If the problem persists, this command will help you open an issue in the Bundler issue tracker with all of the information that we need to help.
+
+### `bundle add`
+
+Finally, you can add gems to your Gemfile directly from the command line, without having to edit your Gemfile first. We've got plans to make this command even better, but this is a good start.
+
+### `bundle pristine`
+
+Just like the `gem pristine` command, the `bundle pristine` command wipes out any changes you have made to the gems installed locally, for testing or debugging reasons, and restores them to a freshly-installed state.