Add version checking logic

[btkelly]

The library should be able to look at various forms of version strings or version codes and deduce which version is higher / lower. This will involve major and minor numbers, ex "1.2.1 vs 1.3.0" and "1.5 vs 2.1" as well as a version code that may be only an integer. The consumer should be able to configure what the library is evaluating, the version name or the version code.

[macklinu]

This library might be useful to us: https://github.com/zafarkhaja/jsemver

[jsibbold]

For 1.0, we'll be using the version code exclusively, as it is required to be both an integer, and to be higher than the previous.

[stkent]

Should this be assigned to a different milestone then? 2.0?

[btkelly]

I think we should just close it for now, might be better to stick with the version code. Thoughts?

[stkent]

Do we care about the iOS implementation, and matching that?

[btkelly]

They have a build number, we were thinking we should use that for iOS

[stkent]

Sounds good!