🚀 go-pugleaf

You can't possibly have said confirmation until the future version exists and can be compared with what will then be the past version.

On the other hand, I think you can be fairly sure that the people doing the engineering work will have compatibility very high on their list of priorities. And yet, should there be major benefits to be drawn from some change or other, then I hope that offer us that major benefit, even if we have to revisit some (even all) of our existing scripts.

If you look back at history, you can see that many 1.5.2 scripts just worked with 2.0, while others needed some adjustment. I'd expect that over tiime, the amount of disruption that occurs with each release will diminish.

On the other hand, if you're going to want to take advantage of the new features in the next release (some of which might even make certain scripts obsolete), then you're going to have to rework the scripts in question.

Dave