bundler 1.15.4 → 1.16.0.pre.1

data/doc/development/README.md

@@ -1,19 +0,0 @@
-# Development
-
-So, you're ready to start contributing to Bundler! You've come to the right place. Here you'll find an overview of how to work on Bundler locally and a description of the process from code to release.
-
-##[Development setup](SETUP.md)
-
-Guidelines for setting up your local development environment.
-
-##[Submitting pull requests](PULL_REQUESTS.md)
-
-An overview of our preferred PR process, including how to run the test suite and what to expect when you submit code for review.
-
-##[Adding new features](NEW_FEATURES.md)
-
-Guidelines for proposing and writing new features for Bundler.
-
-##[Releasing Bundler](RELEASING.md)
-
-A broad-strokes overview of the release process adhered to by the Bundler core team.

data/doc/development/RELEASING.md

@@ -1,9 +0,0 @@
-# Releasing
-
-_Release process documentation is in progress, see [PR 5252](https://github.com/bundler/bundler/pull/5252)._
-
-## Beta testing
-
-Early releases require heavy testing, especially across various system setups. We :heart: testers, and are big fans of anyone who can run `gem install bundler --pre` and try out upcoming releases in their development and staging environments.
-
-There may not always be prereleases or beta versions of Bundler. The Bundler team will tweet from the [@bundlerio account](http://twitter.com/bundlerio) when a prerelease or beta version becomes available. You are also always welcome to try checking out master and building a gem yourself if you want to try out the latest changes.

data/doc/development/SETUP.md

@@ -1,27 +0,0 @@
-# Development setup
-
-Bundler doesn't use a Gemfile to list development dependencies, because when we tried it we couldn't tell if we were awake or it was just another level of dreams. To work on Bundler, you'll probably want to do a couple of things.
-
-1. Install `groff-base` and `graphviz` packages using your package manager, e.g for ubuntu
-
-      $ sudo apt-get install graphviz groff-base -y
-
-   and for OS X (with brew installed)
-
-      $ brew install graphviz homebrew/dupes/groff
-
-2. Install Bundler's development dependencies
-
-      $ bin/rake spec:deps
-
-3. Run the test suite, to make sure things are working
-
-      $ bin/rake spec
-
-4. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
-
-      `$ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'`
-
-## Debugging with `pry`
-
-To dive into the code with Pry: `RUBYOPT=-rpry dbundle` to require pry and then run commands.

data/doc/documentation/README.md

@@ -1,29 +0,0 @@
-# Documentation
-
-Code needs explanation, and sometimes those who know the code well have trouble explaining it to someone just getting into it. Because of that, we welcome documentation suggestions and patches from everyone, especially if they are brand new to using Bundler.
-
-Currently, Bundler has two main sources of documentation:
-
-1. built-in `help` (including usage information and man pages)
-2. [Bundler documentation site](http://bundler.io)
-
-If you have a suggestion or proposed change for [bundler.io](http://bundler.io), please open an issue or send a pull request to the [bundler-site](https://github.com/bundler/bundler-site) repository.
-
-Not sure where to write documentation? In general, follow these guidelines:
-
-* For an explanation of a specific Bundler command (ex: `bundle clean`): make changes to the man pages
-* For longer explanations or usage guides (ex: "Using Bundler with Rails"): create new documentation within the [bundler-site](https://github.com/bundler/bundler-site) repository
-
-If you are unsure where to begin, ping [@feministy](https://github.com/feministy) or [@indirect](https://github.com/indirect) in the Bundler Slack ([get an invite here](../contributing/GETTING_HELP.md)).
-
-## [Writing docs for man pages)](WRITING.md)
-
-If you’d like to submit a patch to the man pages, you're in the right place! Details on editing and previewing changes to man pages can be found here.
-
-## [Documentation vision](VISION.md)
-
-Just like Bundler, we have a grand plan (really, a wish list of sorts) for Bundler documentation. Preview our hopes and dreams for our documentation here.
-
-## Translations
-
-We don't currently have any translations, but please reach out to us if you would like to help get this going.

data/doc/documentation/VISION.md

@@ -1,26 +0,0 @@
-# Documentation vision
-
-Currently, documentation for using Bundler is spread across two places:
-
-1. built-in `help` (including usage information and man pages)
-2. [Bundler documentation site](http://bundler.io)
-
-Additional documentation about using Bundler to publish gems can also be found on the [RubyGems guides](http://guides.rubygems.org/).
-
-## Goals
-
-Bundler documentation should provide users with assistance:
-
-1. Installing Bundler
-2. Using Bundler to manage an application's dependencies
-3. Using Bundler to create, package, and publish gems
-
-Our goal is to provide three types of documentation:
-
-* High level overviews that provide topical guidance
-* Step-by-step tutorials
-* Command-specific reference material for the CLI
-
-Additionally, this documentation should be readily available in a logical place and easy to follow.
-
-Someday, we'd like to create deep-dive reference material about the inner workings of Bundler. However, while this is part of our overall vision for Bundler documentation, it is not the focus of our current work.

data/doc/documentation/WRITING.md

@@ -1,54 +0,0 @@
-# Writing docs for man pages
-
-A primary source of help for Bundler users are the man pages: the output printed when you run `bundle help` (or `bundler help`). These pages can be a little tricky to format and preview, but are pretty straightforward once you get the hang of it.
-
-_Note: `bundler` and `bundle` may be used interchangeably in the CLI. This guide uses `bundle` because it's cuter._
-
-## What goes in man pages?
-
-We use man pages for Bundler commands used in the CLI (command line interface). They can vary in length from large (see `bundle install`) to very short (see `bundle clean`).
-
-To see a list of commands available in the Bundler CLI, type:
-
-      $ bundle help
-
-Our goal is to have a man page for every command.
-
-Don't see a man page for a command? Make a new page and send us a PR! We also welcome edits to existing pages.
-
-## Creating a new man page
-
-To create a new man page, simply create a new `.ronn` file in the `man/` directory.
-
-For example: to create a man page for the command `bundle cookies` (not a real command, sadly), I would create a file `man/bundle-cookies.ronn` and add my documentation there.
-
-## Formatting
-
-Our man pages use ronn formatting, a combination of Markdown and standard man page conventions. It can be a little weird getting used to it at first, especially if you've used Markdown a lot.
-
-[The ronn guide formatting guide](https://rtomayko.github.io/ronn/ronn.7.html) provides a good overview of the common types of formatting.
-
-In general, make your page look like the other pages: utilize sections like `##OPTIONS` and formatting like code blocks and definition lists where appropriate.
-
-If you're not sure if the formatting looks right, that's ok! Make a pull request with what you've got and we'll take a peek.
-
-## Previewing
-
-To preview your changes as they will print out for Bundler users, you'll need to run a series of commands:
-
-```
-$ rake spec:deps
-$ rake man:build
-$ man man/bundle-cookies.1
-```
-
-If you make more changes to `bundle-cookies.ronn`, you'll need to run the `rake man:build` again before previewing.
-
-## Testing
-
-We have tests for our documentation! The most important test file to run before you make your pull request is the one for the `help` command and another for documentation quality.
-
-```
-$ rspec ./spec/commands/help_spec.rb
-$ rspec ./spec/quality_spec.rb
-```

data/task/release.rake

@@ -1,116 +0,0 @@
-# frozen_string_literal: true
-namespace :release do
-  def confirm(prompt = "")
-    loop do
-      print(prompt)
-      print(": ") unless prompt.empty?
-      break if $stdin.gets.strip == "y"
-    end
-  rescue Interrupt
-    abort
-  end
-
-  def gh_api_request(opts)
-    require "net/http"
-    require "json"
-    host = opts.fetch(:host) { "https://api.github.com/" }
-    path = opts.fetch(:path)
-    response = Net::HTTP.get_response(URI.join(host, path))
-
-    links = Hash[*(response["Link"] || "").split(", ").map do |link|
-      href, name = link.match(/<(.*?)>; rel="(\w+)"/).captures
-
-      [name.to_sym, href]
-    end.flatten]
-
-    parsed_response = JSON.parse(response.body)
-
-    if n = links[:next]
-      parsed_response.concat gh_api_request(:host => host, :path => n)
-    end
-
-    parsed_response
-  end
-
-  desc "Make a patch release with the PRs from master in the patch milestone"
-  task :patch, :version do |_t, args|
-    version = args.version
-
-    version ||= begin
-      version = BUNDLER_SPEC.version
-      segments = version.segments
-      if segments.last.is_a?(String)
-        segments << "1"
-      else
-        segments[-1] += 1
-      end
-      segments.join(".")
-    end
-
-    confirm "You are about to release #{version}, currently #{BUNDLER_SPEC.version}"
-
-    milestones = gh_api_request(:path => "repos/bundler/bundler/milestones?state=open")
-    unless patch_milestone = milestones.find {|m| m["title"] == version }
-      abort "failed to find #{version} milestone on GitHub"
-    end
-    prs = gh_api_request(:path => "repos/bundler/bundler/issues?milestone=#{patch_milestone["number"]}&state=all")
-    prs.map! do |pr|
-      abort "#{pr["html_url"]} hasn't been closed yet!" unless pr["state"] == "closed"
-      next unless pr["pull_request"]
-      pr["number"].to_s
-    end
-    prs.compact!
-
-    version_file = "lib/bundler/version.rb"
-    version_contents = File.read(version_file)
-    unless version_contents.sub!(/^(\s*VERSION = )"#{Gem::Version::VERSION_PATTERN}"/, "\\1#{version.to_s.dump}")
-      abort "failed to update #{version_file}, is it in the expected format?"
-    end
-    File.open(version_file, "w") {|f| f.write(version_contents) }
-
-    BUNDLER_SPEC.version = version
-
-    branch = version.split(".", 3)[0, 2].push("stable").join("-")
-    sh("git", "checkout", branch)
-
-    commits = `git log --oneline origin/master --`.split("\n").map {|l| l.split(/\s/, 2) }.reverse
-    commits.select! {|_sha, message| message =~ /(Auto merge of|Merge pull request) ##{Regexp.union(*prs)}/ }
-
-    abort "Could not find commits for all PRs" unless commits.size == prs.size
-
-    unless system("git", "cherry-pick", "-x", "-m", "1", *commits.map(&:first))
-      abort unless system("zsh")
-    end
-
-    prs.each do |pr|
-      system("open", "https://github.com/bundler/bundler/pull/#{pr}")
-      confirm "Add to the changelog"
-    end
-
-    confirm "Update changelog"
-    sh("git", "commit", "-am", "Version #{version} with changelog")
-    sh("rake", "release")
-    sh("git", "checkout", "master")
-    sh("git", "pull")
-    sh("git", "merge", "v#{version}", "--no-edit")
-    sh("git", "push")
-  end
-
-  desc "Open all PRs that have not been included in a stable release"
-  task :open_unreleased_prs do
-    def prs(on = "master")
-      commits = `git log --oneline origin/#{on} --`.split("\n")
-      commits.reverse_each.map {|c| c =~ /(Auto merge of|Merge pull request) #(\d+)/ && $2 }.compact
-    end
-
-    last_stable = `git ls-remote origin`.split("\n").map {|r| r =~ %r{refs/tags/v([\d.]+)$} && $1 }.compact.map {|v| Gem::Version.create(v) }.max
-    last_stable = last_stable.segments[0, 2].<<("stable").join("-")
-
-    in_release = prs("HEAD") - prs(last_stable)
-
-    in_release.each do |pr|
-      system("open", "https://github.com/bundler/bundler/pull/#{pr}")
-      confirm
-    end
-  end
-end