There is nothing here that uses the config file path.
Merge just the weekly release related changes to a new branch
too many nots
Just use regular links to the source code so that release manage can see which file is expected to change and so that link checker will alert us if these files ever get moved.
Upload specific files
Separate the RPM build step...it needs to be watched carfully and may need some further explanation when pre-releases are introduced.
Remove the OSX instructions...we should always be performing the release in a vagrant Fedora20 environment.
Demonstrate sha1sum on the local source package
Try adding some warnings
Add checksum to the list of allowed words
Add `remote_snapshots` to the interface and the in-memory implementation (`IFilesystem`).
More useful in-memory implementation of `IFilesystem.snapshots`.
Add a helper to check for the existence of the filesystem.  Use that to handle the no-snapshots case.
Do incremental pushes.

Change push to first retrieve the snapshots that exist remotely.
Supply this information to the local filesystem reader so it can construct an incremental stream.
Update the filesystem writer so it is capable of receiving incremental streams into the filesystem.
Push has become asynchronous - so propagate Deferred-handling code up the stack from it.
merge master
Debug gunk
Merge remote-tracking branch 'origin/master' into integrate-incremental-push-46
Sketch of implementation.
PushVolume implements IStateChange.
Create utility function that constructs the standard INode provider that
volume managers use to communicate with each other.