REBOL Technologies

Standardizing REBOL Version Numbers

Carl Sassenrath, CTO
REBOL Technologies

Article #0042
Main page || Index || Prior Article [0041] || Next Article [0043] || 0 Comments || Send feedback

Here is a proposal that I would like your comments on: What if we standardized version numbers for all REBOL products? In other words, we would give products like /View the same numbers as the matching version of /Core. (I am sure some of you have already thought of this over the years.)

The advantage is simplicity. A version like 2.5.55 for /View would mean that it is from the same build as Core 2.5.55. This makes life a little easier for developers because something that is new in 2.5.50 (for example) is the same in all products. And, it makes life easier for RT because we don't need to maintain so many product version numbers (there are currently 12 products that can each have a different version) in our build system as well as for answering feedback, bugs, etc. We could also remove the system/core field (added to View alphas earlier this year) because it would no longer be needed.

The disadvantages are that /View would jump from 1.2.x to 2.5.x immediately, and that future products like /Platform would never have a 1.0 or 2.0, but would skip to the current version number. It is also possible that some products like /Core may "skip" versions, such as when a change is only made to /View, but the /Core code remains the same.

Let me know what you think.


Updated 4-Mar-2024   -   Copyright Carl Sassenrath   -   WWW.REBOL.COM   -   Edit   -   Blogger Source Code