Issue #65: incorporate FileTree pharo-2.0 support and turn on pharo-2.0
builds
Update docs to reflect desired bahavior for the `upgrade` command (Issue #11)
Issue #76: start by removing remnants fo `register` command
Issue #76: remove fetch command remnants, add explicit message handling and deferred creation of projectSpec
Issue #76: add MetacelloScriptExecutor class to manage the execution of the list/block args MetacelloScriptEngine executes command against one projectSpec at a time
Issue #76: add logic for string, block and collection arguments
Issue #76: take care of a couple of test failures
Issue #76: revert part of earlier change and adjust test ... get running through different (correct) code path which lead to different behavior
Issue #57: basic restructuring to permit `Metacello registry` style commands

stub out `list` `remove`, and `rest` registry commands
Issue #57 and Issue #76: implement list command, `project:` block still needs work
Issue #57 and Issue #76: block args working for list command

time for tests
Issue #57 and Issue #76: tests for block and collection filter

stalling on name filter, because current implementation is not acting
like a filter ...

I believe that I can use the spec lookup logic for the load, get, and
list ... but I may be stretching things in odd ways ...
Issue #57 and Issue #76: satisfactory implementations for block,

collection, and string args .... list and load appear to be satisfied
with the arrangement.
Issue #79 and Issue #76: add standard exception handlers and standard

lookup for `get` command
Issue #76: double dispatch for resolving string, collection, block args, preparing to control context for new, registry and image
Issue #76: `image` context implemented to select only configurations or baselines that have been loaded

as in the prject is loaded, not just configuration present ... `registry` context tests queued up, but need to have lock/unlock commands implemented to validate test
Issue #76: push code around in preparation for using colelction and block filters for `load` command
Issue #76: `load` and `get` commands can now use collection or block to filter against multiple configs in the designated repo
Issue #76: fiddle with the way the list of roots are returned ...
Issue #76 and Issue #79: revisit implementation of get, add get tests

direct load of projectSpec specified in `get` command ... no lookup in
registry ... update registry after load so that registry has record of
the repository from which the config was loaded