[Octave-bug-tracker] [bug #64977] Explore options for the bytecode interpreter in Octave 9

[John W. Eaton]

Follow-up Comment #14, bug#64977 (group octave):

I originally agreed to put the bytecode interpreter on the default branch
because I thought that if more people were building it and using it, maybe
more people would look at it and do some review.  I also thought that if there
was any chance for it to ultimately become part of Octave then it would be
helpful to have it merged early rather than waiting until it was larger and
probably more complex, making review even more difficult.

In the 5 months since the code was first merged on the default branch we have
obviously seen that some people are trying to use it.  And although compiling
the bytecode interpreter and checking that your Octave code still works when
it is enabled is helpful, it is not a substitute for actual code review.

Since there hasn't been much significant code review in the last 5 months, it
seems to me that moving it back to the default branch now won't increase the
rate of the code review process.

My current assessment is that it is not ready for a stable release and so it
won't be merged back to the default branch until there has been sufficient
review and revision.

As I mentioned earlier, by keeping it on a feature branch it is easy to know
exactly what changes are part of the bytecode interpreter.  That makes it easy
to know what changes need to be reviewed.

No one is taking anything away.  The code is still available in the Octave
source repository and anyone is free to update to and build from the
bytecode-interpreter branch, examine the code, offer review, and help push the
project forward.

Finally, we are all volunteers.  We don't do timelines, milestones, or assign
roles and responsibilities any more than someone wishes to volunteer their
time to work on a specific project and set goals for themselves.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64977>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/