[08:16] <chfoo> yipdw: i'm not using any particular scheme. i'm just incrementing it whenever there's a new feature or bug fix. i intend to keep backwards compatibility for as long as possible
[08:16] <yipdw> chfoo: cool
[08:17] * yipdw would appreciate semver :P
[08:17] <yipdw> though I understand that it's not always feasible when jumping into a codebase
[08:17] <chfoo> i guess 0.0.16 could be relabelled as 1.1.0
[08:19] <chfoo> as long as we're not going backwards i can follow a versioning scheme
[08:19] <yipdw> well
[08:19] <yipdw> only if 0.0.16 isn't compatible with 0.0.15
[08:19] <yipdw> we could call 0.0.16 0.1.0
[08:30] <chfoo> that sounds fine. so the next release should be 0.1.1 since it's only bug fixes.
[10:14] <GLaDOS> 01[13seesaw-kit01] 15chfoo pushed 1 new commit to 06development: 02https://github.com/ArchiveTeam/seesaw-kit/commit/3a1b941d1d3d012694382115d5d7207310ea41ab
[10:14] <GLaDOS> 13seesaw-kit/06development 143a1b941 15Christopher Foo: Adds unittests for version string.
[13:22] <GLaDOS> 01[13seesaw-kit01] 15chfoo pushed 1 new commit to 06master: 02https://github.com/ArchiveTeam/seesaw-kit/commit/ee3b72ff16c95d175927e6659beb6a8a09b86831
[13:22] <GLaDOS> 13seesaw-kit/06master 14ee3b72f 15Christopher Foo: Version 0.1.1...
[13:23] <GLaDOS> 01[13seesaw-kit01] 15chfoo tagged 060.1.1 at 144573a99: 02https://github.com/ArchiveTeam/seesaw-kit/commits/0.1.1