Add slim release support for runner script
Add slim marker file as automatic overlay
Change nodetool path to under releases/<RELEASE_VERSION>/
Add TODO comment to install_upgrade script template
Fix #56 (always-on recursion)

Always-on recursive application of all rebar commands causes too many
issues. Recursive application is required for:
1. dealing with dependencies: get-deps, update-deps, and compile of deps
   right after get-deps or update-deps
2. projects with a riak-like apps/ project structure and dev process

The vast majority of projects are not structured like riak. Therefore,
moving forward it's best to (by default) restrict recursive behavior to
dealing with deps. This commit does that and also adds command line and
rebar.config options for controlling or configuring recursion. Also, we
introduce two meta commands: prepare-deps (equivalent to rebar -r
get-deps compile) and refresh-deps (equivalent to rebar -r update-deps
compile). riak-like projects can extend the list of recursive commands
(to include 'eunit' and 'compile') by adding
{recursive_cmds, [eunit, compile]} to rebar.config.
Fix #226

Running 'rebar list-templates' can take quite a long time, when it has
to search the file system. To fix that, make list-templates not recurse
by default. To enable recursion, run 'rebar -r list-templates'.
Keep compile recursive and update the tests to not pass -r to compile
Merge branch 'tuncer-auto-recursion'
Document skip_apps= and apps=
erlc: fixup log message

Using the filename as a prefix is less readable and inconsistent with
the other log messages.

Before:

DEBUG: src/foo.erl depends on...

After:

DEBUG: Dependencies of src/foo.erl ...
erlc: add test suite
Document require_*_vsn options
Add partial support for Erlang/OTP 17

Allow rebar to compile applications using Erlang/OTP 17 and older
versions.  This patch only provides partial support since the rebar
tool itself must be compiled using an Erlang/OTP version that is older
than 17.
rebar.app: remove superfluous quoting
Fix 'rebar generate' regression (#253)

If the directory we're about to process contains
reltool.config[.script] and the command to be applied is
'generate', then it's safe to process. We do this to retain the
behavior of specifying {sub_dirs, ["rel"]} and have "rebar generate"
pick up rel/reltool.config[.script]. Without this workaround you'd
have to run "rebar -r generate" (which you don't want to do if you
have deps or other sub_dirs) or "cd rel && rebar generate".
Merge pull request #237 from norton/norton-17

Add partial support for Erlang/OTP 17
file_utils: properly report errors (fix #95)

While at it, improve the error message printed by rebar_utils:sh/2.
Merge pull request #254 from tuncer/fix-generate

Fix 'rebar generate' regression (#253)
Fix 'rebar help clean' function_clause error

Missing info(help, clean) in rebar_qc.erl.
Merge pull request #265 from goofansu/fix-qc-help-clean

Fix 'rebar help clean' function_clause error