0.0.1 to 1.0.0 todo items

[dalehenrich]

• [x] make a 0.0.2 release, where the version of tODE uses tag 0.0.? that way I can easily patch gsDevKit and or tODE for users who continue to work with 0.0.2 and old version of tODE ... new version of tODE will be 0.1.x so I can use tag 0.? with 1.0.0
• [ ] release notes
  • [ ] project loading theme
• [x] scripts to support new /sys structure
• [x] tode/sys/default/home/ contents
• [ ] load tode project script based on loadProject script
  • [x] bin/createTodeProjectStone and bin/installTodeProjectStone
  • [ ] projects/magritte3/bin/installMagritte3Stone, etc.
• [ ] /sys/default/bin/validateStoneSysNodes man page updated to include dirs, packages and repos, etc.
• [x] install README edits
  • [X] move tODE details to separate doc
  • [ ] review tODE Getting Started doc (new home) and make sure links are clean
  • [x] include ubunutu system requirements (Issue #22)
  • [x] include fix for Issue #48 in readme
  • [x] web client license blurb (note about free email version of license)
  • [ ] Development Kit projects cleanup
  • [ ] projects readme
  • [ ] tODE project ... just to hook up the tode directory ...
    • [ ] cp /sys/stone/dirs/Tode/tode /sys/local/home/tode
    • [ ] mount @/sys/stone/dirs/Tode/tode /sys/local/home tode
  • [ ] pier3.0.0 (Seaside3.0 and swazoo)
  • [ ] magritte (Seaside3.1 and gem server)
  • [ ] seaside3.1 (zinc and gem server)
  • [ ] zinc 2.4.3.1
  • [ ] magritte3 (Seaside3.1, zinc and gem server)
  • [x] tests/ ... alternate tode boottstrap and pe pointing at dev for tests (better alternative than -branch arg to scripts
  • [x] include Mariano's X11 forwarding trick in os orereqs docs ... along with install instructions if needed

[dalehenrich]

see https://github.com/dalehenrich/tode/issues/106

[dalehenrich]

finally some green ... one green is pretty good ... the failure was an out or memory issue, so I'll bump the default TOC.

The out of memory occured during bash createTodeStone flow 3.2.4 during gsUpgrader of all things .. this has been done thousands of times ... I'd think ...

[dalehenrich]

okay ... the PR run did run out of memory, but did blow up doing a backup during magritte build ... failures during backup are not unexpected on travis

[dalehenrich]

I lovethe smell of passing tests in the morning ... more delogging needed

[dalehenrich]

all green again

[dalehenrich]

checkpoint Magritte tests running green includes build plus running tests