Joseph Hickey

At any rate - going back to the original question here - as a __developer__, I'm most interested in, and pay most attention to item (7) from the initial summary...

> Beyond that, I struggle to understand what additional build numbers, strings, etc gives us. For reference, when I say enhanced versioning I'm referring to git describe, build username, and...

BTW - item (2) in my comment is easily solvable, its just a matter of providing a hook so the user can easily tie into whatever the equivalent of "git...

The only issue is that the "last official release" has 3 numbers not just 2. So how can one differentiate a development build based off 6.7.0 vs 6.7.1? This is...

I still would think we'd want the MAJOR.MINOR.REV content in the TLM packet to be true/correct - this is why I don't like clobbering/overriding the REV field - it's relevant....

> Is it worth changing version reporting in TLM for development versions 3 times in 3 releases vs just 6.7 cycle being unique (since I broke the pattern) just to...

And just to note - whenever bootes is officially released we have to change the version info anyway.

Yes, we'd need to add PSP info to the ES HK TLM. The mission rev is already in there though, for OSAL and CFE at least. The only change is...

To summarize what I'd like to do here, each module (OSAL, PSP, CFE) would publicize the following info via their API/headers: - Numeric version info as 4-tuple (MAJOR.MINOR.REV.MISSION_REV), 8 bits...

@astrogeco - this is why the original testing of PR nasa/osal#508 didn't show an issue - either locally for me or in CI. It was noticed by a user who...