Increment several core infrastructure dependencies to current releases,
using explicit release numbers: backbone, chai, sinon, sinon-chai,
chai-jquery.  This yields 5 new test failures.

(We are not yet incrementing zepto from 1.0rc1 to 1.0. That yields
several more test failures, to be examined in a subsequent phase of this
effort.)

This yields
Do spiderOakApp.initialize() in beforeEach() so that the test does not
fail when run separately from the other tests.
Some small changes to simplify debugging.
Identified the problem causing failure of .addOne to be called on
total fetch of a collection.  Per the backbone [Change
Log](http://backbonejs.org/#changelog) documentation for the 1.0.0
version, collection update now does a .set rather than a .reset.

This is a quick workaround: pass {reset: true} in the fetch
options.  I'm going to next see how we could change our code to fully
use the new approach.
Implement an application-specific CollectionsBase with a fetch that
passes {reset: true} (if there's not an explicit reset option setting
present) in to the Backbone.Collections.fetch, and extend all our apps
collections from that base.
Upgrade Zepto from v1.0rc1 to v1.0, and handle the fallout in subsequent
checkins.
Loosen fakeServer login/logout url match rules to allow for
cache-preventing query parameters on the urls.  We do that by using
match regular expressions which disregard any query parameters.  They
are designed to work whether or not any query parameters are present.

It appears that Zepto 1.0 is surprising us by properly respecting
caching directive, while 1.0rc1 neglected to do so.  This accounts for
that.
Adjust matche expressions for url-encoded strings so that sequences of
spaces are all replaced by "+" signs, rather than just the first one.

My guess is that we were accommodating an url encoding flaw in Zepto 1.0rc1
that only replaced the first of a sequences of spaces with a "+", and we
are now tracking the correct substitution of the entire sequence of
spaces with pluses.
Better incorporate backbone v 1.0 migration to doing a 'set' rather than
'reset' on fetch.

The set is already incorporating the missing items, so we don't actually
need to propagate a 'reset' in fetch.

Some views do, however, depend on getting a 'complete' event in order to
clear the "loading" indicator.  To accomplish that, we use the new
CollectionBase collection to trigger a 'complete' event, and then catch
the collection's complete event in the views to trigger a complete event
in the view.

That's all the new CollectionBase needs to do, however - no special
fetch - and the view's attention to the "reset" event is no longer
necessary.
Upgrade to Backbone 1.1, handle the fallout next.
Add our own ViewBase so we can wire in this.options, which is no longer
implicitly conveyed in 1.1 - per the release notes:

  Backbone Views no longer automatically attach options passed to the
  constructor as this.options, but you can do it yourself if you
  prefer.

Having our own versions of the base elements is looking like the right
thing to do.  It will make it trivial to handle future such
accommodations (if backbone continues to churn so badly), and would
provide a basis for distilling common functionality, to reduce code
duplication.  I'm going to add an empty one for models, next.
Some small, incidental changes - base element description comments.
Implement an app-specific ModelBase and use it for all models in the app:
- make it easier to accommodate changes to model in future backbone releases
- use it to provide model.composedUrl, rather than tinkering with Backbone.model
- ensure that we're using the app-specific version everywhere...
- including in tests,
- and including in app-specific collections.
Fix My ShareRooms so that password-protection is respected in listing
and visit.  It depends on the no-longer issued "reset" event - use
the "complete" event that we're propagating, instead.
Include final note about recent developments to the log document.
Remove the progress/details log, we don't need it as part of the ongoing
project.
Merge pull request #343 from SpiderOak/issue-79-unpin-backbone

Issue 79 unpin backbone