more detaled wip on name coming from package.js
tests and minor fixes for --name
Use 15-second timeout for service connections

This should reduce failures to send package stats.
update fstream/tar to fix tarball crash

https://github.com/npm/fstream/issues/26

We were working around this before, but this is a better fix. Plus might
be a (probably unobservable?) performance improvement since we do fewer
fs ops.
Remove work-around for fstream bug

Now fixed upstream.
Merge branch 'upgrade-tar-fstream' into devel
output safety
mark tests from checkout if they use the test server due to release duplication issues
version bump for rc10
Fix client side reload race condition

There was a race condition between the bundle process and when we established
the client watch set. We now store the future for the old bundle process so
that it cannot be invalidated.
Fix client side reload race condition

There was a race condition between the bundle process and when we established
the client watch set. We now store the future for the old bundle process so
that it cannot be invalidated.
wrap opennign server connection in a try/catch block from refresh
adjust which tests are from checkout
Change meetup /members URL.

Apparently secure.meetup.com doesn't work anymore.
Change meetup /members URL.

Apparently secure.meetup.com doesn't work anymore.
don't crash when removing a nonexistent package
Make slow operations more bearable with Patience

Introduces a "Patience" class which lets CPU-bound operations like the
constraint solver yield every so often, and print messages if an
operation (CPU-bound or not) are taken or not.
one weird hack to maybe have better messages for nonexistent packages
bad merge diffs
Lower version numbers of some third-party packages

We haven't yet decided how we want to do versioning for packages that
mostly just wrap non-Meteor code that has its own version numbers. We
might stick to totally-unrelated version numbers (and maybe add a
"wrapped version" field that gets displayed in the upgrade/downgrade
messages?), or change to matching upstream versions (with techniques for
dealing with changes to packaging, a la debian_revision), or something
different.

But since changing to match upstream versions is a possibility, let's
make sure that that operation won't be viewed as a "downgrade" by
updating the wrapped packages whose upstream versions are 0.*.