Merge branch 'devel' into release-0.6.2
Merge branch 'devel' into release-0.6.2
Use npm instal --force to get around NPM cache corruption bug.
Revert "Use npm instal --force to get around NPM cache corruption bug."

This reverts commit 7825ae7845026302ff0d6cb47d8b60ca63f2d43b.

test_bundler_npm.js (even after an obvious fix is applied to an unrelated
problem) fails a noticeable percentage of the time in the "bundle multiple apps
in parallel" test. It does not appear to fail on the node-0.10 branch, so will
apply this there instead.
Support EJSON.clone(arguments).

This enables (eg) Meteor.apply('foo', arguments). Fixes #946.
More fixes for homedirs with spaces in their name.

Also, go on a quoting spree on places that weren't problems, so no one copies bad bash.
Update apps to 0.6.2-rc3
Tag History.md with new version number.
Notices and banner.
Only define Collection.prototype.allow/deny on the server.

Motivated by finding a user created package which added a file
only on the client, in which there were calls to .allow. This way
they would get an error.
banner text
Bump version numbers on apps.
Merge branch 'release-0.6.2'
Merge branch 'master' into devel
Revert "Only define Collection.prototype.allow/deny on the server."

This reverts commit 2294da1297423147011ffd8441092026abdcd26a.
added file for fiber_helper style stubs on the client
Test for observe ordering in minimongo on server.

Currently failing.  Test first wheeeee!
Minimongo now uses a queue to manage observes

What this means for the user is that now, both on the server and the client, if
you look at a minimongo-backed collection from an observe/observeChanges
callback, you'll see a consistent view of it -- you'll never see it in the
middle of an update, for instance.

Furthermore, server!minimongo no longer has stubs, just future waits or
callbacks, your choice.
Just don't provide stubs for collection methods on server; test.

Test is for insert on server-to-server DDP minimongo side.
Queue behavior v1, flush until mark