The Rhino versioning scheme

[Charles Lowell]

Originally when I created the gem, I thought that the major version number would track the rhino version. In retrospect this was bone-headed. Should we go ahead and ditch it?

cheers,

Charles

Charles Lowell 

thefrontside.net | twitter: @cowboyd | github: cowboyd

(p) +1.512.207.0229 (f) +1.512.374.0777

[Karol Bucek]

 Right, it's unfortunate (but not that bad) I was kinda hoping you would bring that up during the "big rewrite" https://github.com/cowboyd/therubyrhino/pull/10

Than on the other hand, it kept me motivated for doing backward compatibility (I still did some non-compatible changes in the last release you've put out yesterday 1.73.3 but kept them fully backward compatible with a deprecation printed). Thus I think it's fine, but once those deprecations should go and then it probably is time for a 2.0 !

Currently we're still "just" catching up with V8 + TRR. I would wait for a major event like if a Rhino 1.8 release (ever) happens or we hit bugs that would require us to build our own .jar, or we got tired of maintaining compatibility as it gets in our way slightly complicating further development ...

K.