Update History.md
Split out android prereqs from android bundle installation
Creating android --getready command
Merge branch '0.9.3.1' into 0.9.4-pre.2

Conflicts:
	History.md
	packages/meteor-tool/package.js
	packages/package-version-parser/package.js
	scripts/admin/banners.json
	scripts/admin/meteor-release-experimental.json
Check for meteor avd
Work around fstream weirdnesses.

Before this fix, we were producing tarballs that npm 'tar' couldn't
untar if the first file inside the top-level directory was not
writeable. (Which was indeed the case since the unipackage -> isopack
change, which resulted in isopack.json being the first file in built
package tarballs.) See comment for more explanation.
Bump minimongo version number
Bump all of the version numbers again, to republish with the unipackage.json fix
Bump release number
don't forget to write the format for old-style unipackage.json
Bump all version numbers again after cherry-picking unipackage fix
Publish versioned dependencies of core packages

When publishing a core package, you’re allowed to omit version numbers in package.js.  With this change, we determine the correct versions of all the dependent packages based on the current checkout, and we send them to troposphere (instead of core packages having “null” constraints on their dependencies).

We throw an error if you have any missing version constraints on your package dependencies and you are not using versionsFrom or publishing a core package from a checkout.

We’ve already fixed this (no constraints on core package deps) retroactively in troposphere.

It speeds up the constraint solver by orders of magnitude when publishing a package.
Fixed srp package.js
Add version constraing to bootstrap use
Bump meteor-tool version
Pass the appId to the application process in an env variable

Since it is passed only in the development mode it can be used for nifty things
like distinguishing mobile apps by a tuple of (id, server-url)
Work around fstream weirdnesses.

Before this fix, we were producing tarballs that npm 'tar' couldn't
untar if the first file inside the top-level directory was not
writeable. (Which was indeed the case since the unipackage -> isopack
change, which resulted in isopack.json being the first file in built
package tarballs.) See comment for more explanation.
Whitespace
Fix building for mobile targets w/o a mobile control file
Fix actually using the new config.xml in the new mobile build flow