Create new version scheme for new features

[gbrail]

We are working on some new features related to ECMAScript 6, and I think that the current versioning scheme is not serving us well.

I propose that we create the following plan:

Rhino 2.0.0 will have ECMAScript 6 compliance, whenever we can get there. In this version, the default language version would be "VERSION_ES_6."

Rhino 1.9.0 will be the next version (successor to 1.7R5pre4). It will include partial ES 6 features that can be enabled by setting the language version, but they would be off by default unless the version is set. The default version would be VERSION_1_8.

Additional versions could be created at 1.9.1, 1.9.2, and so on, and we will abandon the "pre" designation.

This way the Rhino version number is decoupled from the language version number.

Please let me know what you think about this...

[hrj]

I am not familiar with the history of Rhino versioning and not deeply familiar with ES versions either.

However, I will take this opportunity to suggest that this project could get a slight renaming to clarify that it is a fork. Something like Rhinosaurus or Rhinosome, or better.

Otherwise, Rhino 1.9 or Rhino 2.0 is going to be very confusing if the original Rhino wakes up for some reason and publishes its own 1.9 version.

[gbrail]

Thanks for the concern and for seeing this.

I've been emailing a few Mozilla people and I'll try to get some info from
them before we go too far with this.

On Wed, Jan 14, 2015 at 10:07 AM, hrj notifications@github.com wrote:

I am not familiar with the history of Rhino versioning and not deeply
familiar with ES versions either.

However, I will take this opportunity to suggest that this project could
get a slight renaming to clarify that it is a fork. Something like
Rhinosaurus or Rhinosome, or better.

Otherwise, Rhino 1.9 or Rhino 2.0 is going to be very confusing if the
original Rhino wakes up for some reason and publishes its own 1.9 version.

—
Reply to this email directly or view it on GitHub
#27 (comment).

greg brail | apigee https://apigee.com/ | twitter @gbrail
http://twitter.com/gbrail