SERVER-6821 - test had a > vs >= bug making it flaky
SERVER:6810: free nonce once released from tsp
Fix balancer when running mixed 2.2 and 2.0 shards. SERVER-6902

_recvChunkStart command on 2.2 expects a shardKeyPattern argument. 2.0 mongods
don't send that, which breaks migrations.  This fixes this by assuming the shard
key has the same pattern as the range specifiers in Helpers::removeRange when
the shardKeyPattern isn't explicitly provided.
SERVER-6878 Clean distinct3.js and make evalb.js more robust.
SERVER-6948 Make it safe to call commitIfNeeded() from a read lock
SERVER-6960 Always link object files and static archives in the same order.

SCons (correctly) considers two link command lines different if the order of
object files or static libraries changes.  As a result, the libdeps system needs
to produce consistent ordering of these files in the $_LIBDEPS expansion.  This
patch achieves this by sorting the _LIBDEPS candidate expansion by the string
name of the expanded objects.

This problem is akin to that from SERVER-5254, which was solved in a similar
manner.
SERVER-6931 Don't attempt to look up a cursor using an invalid id.  Prevents an occasional incorrect warning message.
SERVER-6856 do not read past the end of a record
SERVER-6834 wait for all stopped nodes to be down in test

Wait for all the nodes that we stopped to be seen as { ok : false }
before proceeding to the next part of the test.
SERVER-6832 make 'move-top-chunk' heuristic work with prefix shard keys
SERVER-6717 use log() in msgasserted() instead of tlog()
SERVER-5890 do not require space after comma in Digest HTTP header

Change the regular expression used to parse the Digest line sent in the
HTTP GET headers for authentication so that whitespace following a comma
is optional (and can be other than a single space if it appears).
SERVER-6930 trim minvalid document to just ts/timestamp and h/hash for performance/freespace benefits
SERVER-6930 append correct format for timestamp
Fix for SERVER-6672:

Added logic in the oplog application batching algorithm to end the batch early if the we see an op that is too new to be applied with respect to the slaveDelay.
Flush journal after every oplog write (if necessary) SERVER-6816
SERVER-6816 cap the batch on the journal commit limit

Calling commitIfNeeded() in a local db lock is prohibited so I removed it.  Instead, we will make the batch sizes smaller than the journal commit limit size to avoid DR102 messages.
SERVER-6816 add a 5 sec time limit to replication batches

Even with a byte cap on replication batches, it is still possible to
batch up a large number of writes which can take a long time to apply.
This commit ensures that batches do not get too large.  5 seconds' worth
of replicated ops over the network will take much less than 5 seconds to
write to the database.

Conflicts:

	src/mongo/db/repl/rs_sync.cpp
SERVER-7003 fix migrations in the presence of active deletions
SERVER-6816 cap repl batches at 1 second or 5000 ops