remove history entry for nonexistent 0.6.4.2
Bump versions for 1.0.2.
Fix app build for Cordova

Caught by a zillion tests, oops.  But not by --prepare-app!
1.0.2-rc.2
"Fix" bizarre memory corruption (?) bug

See #3285.  For some reason, in some mostly-replicatable circumstances,
this is necessary.  Clearly some sort of V8/Node/Fibers bug.
1.0.2-rc.3
rough draft of History.md for 1.0.2
Fall back to fs.watchFile if pathwatcher.watch does not work.

Fixes #3284.
Allow forcing fs.watchFile with an environment variable.
Be more specific about how to run meteor update
Package version bumps.
Move pathwatcher fallback message to debug level
Don't force external links to open in a new tab

Overriding user preference is a bad idea from a usability point of view. Just allow people to decide for themselves whether they want to navigate away to another page or open the link in a new tab using the controls provided them by the browser (eg. cmd-click, or the options in the right click menu).

This also fixes the situation where someone might want to open an external link in the same tab, which is currently made impossible.
Make deny, allow example clear as to client/server

As per explanation from Avital Oliver in meteor-talk, I suggest making this change in the doc to make it more clear that the example does not need to reside on *both* the client and server. The title of the sections (deny, allow) from the autoApiBox specify "server". The example got me confused as is.
Avoid pathwatcher.watch failures in testDirectory.
Create temporary pathwatcher test file in app directory.

Previously we were testing pathwatcher.watch by creating a file in
.meteor/local, but developers using Vagrant VMs often mount .meteor on a
different (non-network) file system, for Mongo's sake.

Writing the file directly in the app directory increases the likelihood
that it will interact with pathwatcher in the same way as other source
files the developer will be editing.

Conflicts from devel:
	tools/safe-pathwatcher.js
Run file watching tests with both pathwatcher.watch and fs.watchFile.

Running the two versions of the test in parallel is safe because they run
in separate processes, and a good idea because it cuts the time taken by
the test in half, from 36sec to 19sec.

Conflicts from devel:
	tools/tests/old.js
Fix pathwatcher fallback tests

- Future.wait does not throw
- any non-empty env var counts as true
Clear password reset tokens on password change

Conflicts from devel:
	History.md
Disallow EJSON custom types as replacement documents in updates