0.9.4

PR #10 with fix Issue #6:

• old-style STON (STON[Reader|Writer]) supports which means handicapped handling of multi-byte characters
• old-style GemStone/tODE support (STON051[Reader|Writer]) where UTF8 encoding is supplied at individual string level and codePoints over 126 are escaped
• new-style GemStone/TODE support (STON091[Reader|Writer]) where UTF8 encoding is done for the entire STON string, no character escaping is necessary (UTF8uses 8-bit ASCII characters), if escaped characters are encountered, assumption is made that STON was encoded using old-style GemStone/tODE (STON051[Reader|Writer])
• new-style STON (STONUtd8[Reader|Writer]) support where UTF8 encoding is done for the entire STON string, no character escaping is used and on decode escaped codePoints signal an error ...
• support both pharo and gemstone on the gemstone branch ...

In support of dalehenrich/tode#175.

0.9.3

final gemstone_dev tag for Issue #6. Basically a preview of what can be expected with PR #10....buys me some time to test tODE upgrade scenarios before final merge ... aimed at v0.9.4

0.9.2

another intermediate release for Issue #6 ... tag on gemstone_dev for use by tODE (dalehenrich/tode#175) ... this time we are marking the point at which the pharo_dev branch was "merged" into the gemstone_dev branch new platform-specific packages, etc. won't need the pharo-* tags anymore

0.9.1

intermediate release for Issue #6 ... tag on gemstone_dev for use by tODE (dalehenrich/tode#175)

pharo-0.9.1

intermediate release of work on Issue #6: tagging pharo_dev branch for use by tODE (dalehenrich/tode#175)

pharo-0.9.0

port STON 0.9 from svenvc/ston ... on pharo branch

0.9.0

port STON 0.9 from svenvc/ston ... use semantic version patterm x.x.x for tag name

0.5.1

Tag for commit that precedes the work to port STON 0.9 to GemStone

0.5

corresponds to STON 0.5

pharo-0.5.0

additional tag for pharo release .... equivalent to pharo-0.5, but using semantic versioning x.x.x version number