Merge branch 'dev' into gemstone3.1
Issue #2: remove the old GsCore project references and replace with a
single reference to GLASS1

- master branch reference for now
- using a lock is preferred way to manage GLASS,
  especially with baseline refs.
- with ConfigurationOfGsDevKit we can transition back to a
  version reference .... if needed
Issue #2: not sure I want to go with the GLASS1 reference ... pull back and then do work on a branch ...
sync with smalltalkhub
Merge branch 'master' into gemstone3.1 (leaving out comanche adaptor)

* master:
  sync with smalltalkhub
sync with smalltalkhub
Merge branch 'master' into gemstone3.1

* master:
  sync with smalltalkhub
fixed a test
Merge branch 'master' into gemstone3.1

* master:
  fixed a test
updating travis CI scripts
renamed travis script
fixing travis
still fixing travis...
fixing more travis
Revert "Issue #2: not sure I want to go with the GLASS1 reference ... pull back and then do work on a branch ..."

This reverts commit 4b6a9f61ddd5bf4ccd19867a550182f5f9fe5712.
Revert "Revert "Issue #2: not sure I want to go with the GLASS1 reference ... pull back and then do work on a branch ...""

This reverts commit 42e28c5ee44de94ef53af3975a4f0ef3ff98b791.
explicitly load GLASS1 in Travis rather than referencing it from the Baseline which seems to break
applying gsdeployer magic potion
adapt load instructions
fixes for the README