Remove unused references
Added Ef5Repository which has an EF5 rather than EF4 dependency. Code is essentially duplicated from EfRepository and there are no tests in place yet. Needed it quickly -- so I pooped it out.
Updated summary reference from Ef to Ef5
Moving AbbFabric and Memcached providers into separate projects

This way the base repository is not dependent on those assemblies and
can be used with inmemory or no caching providers out of the box.  Then
the separate dlls can be added for memcached or whatever you want to
use.

Also started messing with NuGet stuff so some smaple test packages are
in the source now.

References:

http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package

http://stackoverflow.com/questions/10240029/how-to-install-a-nuget-package-nupkg-file-locally
Updated InMemoryRepository to use ConcurrentDictionary

Was going to switch the list to a dictionary since it's a better fit
since we are doing lookups by key for a lot of it, but the
ConcurrentDictionary is thread-safe so went that route.
Change accessibility of Specification's Predicate setter from internal to public. This is necessary in order to set complex Predicate in custom Spec's constructor rather than passing simple predicate to base Specification constructor.
Added Redis caching provider

NOT TESTED YET but builds fine.  I haven;t installed redis yet but will
and will test later.
package config got unchecked by accident
Added Windows Azure Shared Caching provider

It seems like this is the same code as the AppFabric stuff so I'm a bit
confused.  Again haven't tested it yet.

Seems like the AppFabric stuff was used as the start for the azure
caching so they share things, but the code really is identical even
though I included different NuGet packages for them.

http://msdn.microsoft.com/en-us/library/windowsazure/gg185678.aspx
Added nuget specs and packages

for Repository, Ef5, InMemory and Memcached caching provider
Updated assembly versions to match NuGet version
Created power shell script to automate nuget builds

It's convention based.  It goes through each sub-directory in /nuget/
and updates the version in the nuspec file based on the nuspec.template,
then uses that new file to create a new package and puts that file into
the proper nuget directory.  Then we will upload through the website as
normal.
Update nuget packages used within #Repos

Updated EnyimMemcached, NUnit and MongoDbSharpDriver
Verified all integration tests still pass
Assembly # update to match nuget version #

I'm guessing there is an auotmated way to do this?
Cleaned up some resharper suggestions
GetAllQuery and FindAllQuery to return IQueryable

These are internal methods and by returning IQueryable we can keep it as
a query (and on the server side if the LINQ provider does it that way)
until the last minute.  Previously we were returning IEnumerable and had
a call to ToList() in these methods and so when doing a selector, each
entire entity was returned and then the selector was supplied.  This
wasn't ideal because more data was transferred over the wire than needed
to be.

So now the FindAll and QueryAll that take a selector, call the
GetAllQuery or FindAllQuery which keeps it as a Quyerable and then adds
the .Select() part so it's part of the query.  Then the FindAll or
GetAll calls ToList() to take it from the server side and returne the
actual results.
New 1.0.1.0 nuget packages becasue of the Select logic fix
InMemory nuget package didn't have dependcy set
Fix caching bug when variables are used in the query instead of constants

I added a HashGeneratorTests unit test and added some various kinds of
predicates that include constants, variables, list variables.  We should
keep expanding this to make sure it covers everything we can think of.
Added reference to Pet Montgomery's excellent blog post that helped me solve this issue

for reference again:
http://petemontgomery.wordpress.com/2008/08/07/caching-the-results-of-linq-queries/