SwissMicros Calculator Forum

rprosperi wrote: ↑

Wed Jan 29, 2020 1:44 am

The latest manuals I see in gitlab are version 0_14, though update time of "8 hours ago" confirm they are fresh. Isn't the version number typically incremented each release?

No, it isn't. Else we'd be at v0.1xx or greater. You're right in principle though. A proper document management by version number alone would increment said number with each release. If we were forced to specify we have a doc management by version number and date - please see the Release Notes.

Addendum: As soon as we launch some physical calculators we'll behave and do document management following the simple textbooks for sake of ... simplicity ... and clarity. Almost promised.

Alas, I'm afraid there are still a lot of functions to be coded - some 50% I'd guess. We're still open to supporters and collaborators (sounds like labor quite rightly), so whoever has the necessary capabilities and spare time to dedicate to this project (and looks for eternal fame in the community ) shall feel free to apply for these tasks. ([:-) ((Ducks and covers to be not slain by the sheer amount of applications))

Walter wrote: ↑

Wed Jan 29, 2020 9:47 am

rprosperi wrote: ↑

Wed Jan 29, 2020 1:44 am

The latest manuals I see in gitlab are version 0_14, though update time of "8 hours ago" confirm they are fresh. Isn't the version number typically incremented each release?

No, it isn't. Else we'd be at v0.1xx or greater. You're right in principle though. A proper document management by version number alone would increment said number with each release. If we were forced to specify we have a doc management by version number and date - please see the Release Notes.

Version 0_14 reads like major version 0, minor version 14 to me. Appending a third (patch) number (https://semver.org), perhaps also a fourth build number, has been observed in the wild - and might prove helpful.

H2X wrote: ↑

Wed Jan 29, 2020 6:54 pm

Walter wrote: ↑

Wed Jan 29, 2020 9:47 am

rprosperi wrote: ↑

Wed Jan 29, 2020 1:44 am

The latest manuals I see in gitlab are version 0_14, though update time of "8 hours ago" confirm they are fresh. Isn't the version number typically incremented each release?

No, it isn't. Else we'd be at v0.1xx or greater. You're right in principle though. A proper document management by version number alone would increment said number with each release. If we were forced to specify we have a doc management by version number and date - please see the Release Notes.

Version 0_14 reads like major version 0, minor version 14 to me. Appending a third (patch) number (https://semver.org), perhaps also a fourth build number, has been observed in the wild - and might prove helpful.

Nothing's as free as numbers. And any system can be elaborated in a way you need a full-time-equivalent for maintaining. But cui bono? So far, numbering the manual versions is just for separating particular steps in our documentation and/or SW development. You can call it an internal version number, for the team only. Once we'll be "in the wild" ... (please see my previous post).

Walter wrote: ↑

Wed Jan 29, 2020 7:06 pm

H2X wrote: ↑

Wed Jan 29, 2020 6:54 pm

Walter wrote: ↑

Wed Jan 29, 2020 9:47 am

No, it isn't. Else we'd be at v0.1xx or greater. You're right in principle though. A proper document management by version number alone would increment said number with each release. If we were forced to specify we have a doc management by version number and date - please see the Release Notes.

Version 0_14 reads like major version 0, minor version 14 to me. Appending a third (patch) number (https://semver.org), perhaps also a fourth build number, has been observed in the wild - and might prove helpful.

Nothing's as free as numbers. And any system can be elaborated in a way you need a full-time-equivalent for maintaining. But cui bono? So far, numbering the manual versions is just for separating particular steps in our documentation and/or SW development. You can call it an internal version number, for the team only. Once we'll be "in the wild" ... (please see my previous post).

Absolutely. And I have no complaints (and you would of course quite rightly ignore them if I had). My only point might that https://semver.org might has some adoption, perhaps enough so to ease the maintenance burden should one find it suitable and choose to adopt it oneself.

Now back to minding some business of my own...

When we have some calculators "in the wild" we'll most probably have something like n.m bxxx (major_release_number dot minor_release_number blank b build_number) like we have with the WP34S already. I don't like reinventing the wheel as long as it's round enough.

The build number was an artefact of the source code control system the 34S used subversion. The 43S uses git which has a hash as a version code -- i.e. there is no build number. We'll need to be more careful with the version numbering.

Pauli

Thanks for the remark. So we'll have to find something equivalent replacing the old build number.

Walter wrote: ↑

Thu Jan 30, 2020 9:37 am

So we'll have to find something equivalent replacing the old build number.

Why? What's wrong with the major.minor versioning?

pauli wrote: ↑

Thu Jan 30, 2020 10:17 am

Walter wrote: ↑

Thu Jan 30, 2020 9:37 am

So we'll have to find something equivalent replacing the old build number.

Why? What's wrong with the major.minor versioning?

Nothing whatsoever, as long as one is not bothered by the different things appearing to be the same when they shouldn't?

pauli wrote: ↑

Thu Jan 30, 2020 10:17 am

Walter wrote: ↑

Thu Jan 30, 2020 9:37 am

So we'll have to find something equivalent replacing the old build number.

Why? What's wrong with the major.minor versioning?

Doc-wise: nothing.

OTOH, repairing bugs etc. in the SW, do we want to wait for another minor release until we're allowed uploading a corrected/updated wp43s.exe ? How do we differentiate different SW editions complying to the same documentation? If we want to increment the minor_release_number with each and every little bug repaired (actually with each new wp43s.exe) then we'd have to update the documentation simultaneously just to keep this number in line with the SW although the contents of the docs remain unchanged except that number. Just asking what you want...