On 14.03.2020 21:51, Enrico Sorichetti via Oorexx-devel wrote: > There is a clash in the nomenclature used by IBM software development > And the one used in the *ix word > > The IBM terminology is explained here > https://www.ibm.com/support/pages/vrmf-maintenance-stream-delivery-vehicle-terminology-explanation
Wow, very helpful, thank you very much Enrico! > On the other side the *ix is a bit murkier due also to the confusion about > library versioning > > The terms used by CMAKE are > > PROJECT_VERSION > PROJECT_VERSION_MAJOR > PROJECT_VERSION_MINOR > PROJECT_VERSION_PATCH > PROJECT_VERSION_TWEAK > > Looks like ooRexx used a mix of the three > > So it seem reasonable to use > VERSION for the triplet > MAJOR_VERSION for the first level > RELEASE > MODIFICATON > For the rest > > The fourth level in the iBM world > Would be the maintenance level, > But it would not apply to the whole package , but only to the single > components > > In the repository structure of the PC world > The fourth level should be the revision for SVN based > Or the hash for GIT/Mercurial repositories > > And that’ s what I display in my tweaked Rexx <version> > Revision : Git, hash[318c73b+], commits(29), date[2020-02-01 16:10:32 +0100] > The same for Mercurial ( HG instead of GIT ) > > For SVN it would be > Revision : SVN, revision[1234567+], date[2020-02-01 16:10:32 +0100] Wow, this is really a *very* interesting and helpful (giving the exact date and time of the revision) piece of information and even includes the source code control system with the respective version/commit values!! > The revision is roughly equivalent to the commit count > > The plus at the end of the hash, revision tells that there are changes not > committed > > Going back to the subject… > > In reality nobody cares about the single component names > In the IBM world when talking about some software version > The triplet is reported > > in some cases the IBM supports ask > But only for customer support and maintenance Well, my stance is to follow the Rexx philosophy: make it easy to the human to understand and use the language. For non-IBMers the terminology is not obvious. Maybe the CMAKE terminology has become more known in the meantime? What I would be looking for would be some terminology that self-documents that the pieces belong together and incurs a sequence, which is not the case with "major_version", "modification", "release" (vs. "version"). Hence the request to change these names such that one does not need to look up a book or research the internet, but rather inferring the meaning and position right from the names. ---rony
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
