explain that we are not supporting autoLaunch=false anymore

CHANGELOG.md

@@ -24,6 +24,7 @@ tests.
   the project)
 - add capability validation on the protocol and driver level
 - Appium now requires Node 0.12 as a minimum Node version
+- (breaking) remove the 'autoLaunch' capability since it added a significant amount of complexity to the startup flow and Appium shouldn't be responsible for this kind of use case
 
 #### iOS
 - add Tapster support for some more touch methods

docs/en/writing-running-appium/caps.md

@@ -11,7 +11,6 @@
 |`app`|The absolute local path _or_ remote http URL to an `.ipa` or `.apk` file, or a `.zip` containing one of these. Appium will attempt to install this app binary on the appropriate device first. Note that this capability is not required for Android if you specify `appPackage` and `appActivity` capabilities (see below). Incompatible with `browserName`.|`/abs/path/to/my.apk` or `http://myapp.com/app.ipa`|
 |`browserName`|Name of mobile web browser to automate. Should be an empty string if automating an app instead.|'Safari' for iOS and 'Chrome', 'Chromium', or 'Browser' for Android|
 |`newCommandTimeout`|How long (in seconds) Appium will wait for a new command from the client before assuming the client quit and ending the session|e.g. `60`|
-|`autoLaunch`|Whether to have Appium install and launch the app automatically. Default `true`|`true`, `false`|
 |`language`| (Sim/Emu-only) Language to set for the simulator / emulator |e.g. `fr`|
 |`locale`| (Sim/Emu-only) Locale to set for the simulator / emulator |e.g. `fr_CA`|
 |`udid`| Unique device identifier of the connected physical device|e.g. `1ae203187fc012g`|