Version Numbers

[bensuffolk]

I noticed that we have gone from Major.Minor.Patch[-rcN] e.g. 0.7.0-rc13 to Major.Minor.Build.Revision e.g. 0.7.0.1

I'm wondering why did we make that change?

[fvanroie]

Because -rcxx doesn't mean anything anymore at this point, an plain number works as well.

[bensuffolk]

That’s fair enough, just wanted to check this is a permanent change before I update my software that connects with it as it’s currently not functioning with the new format.

[fvanroie]

I didn't think 0.7.0.1 would be an issue as a version number, it looked better then 0.7.0-rc14 etc.
I'm open to alternatives, but for me this works... The -rc moniker was always meant to be temporary, and got out of hand.

[bensuffolk]

It’s fine, just not how my code parses version strings that’s all. I get it’s good to be out of release candidate mode, it’s been a while and like you say it starts to get meaningless.

do we have a roadmap for what the features we are aiming for with a change to build numbers? I.e what’s the target to get to 0.7.1

[dison4linux]

Where are these versions such as 0.7.0.1 that you mentioned?
The latest I see on GitHub is 0.7.0-rc13 which is over a year old.

[fvanroie]

You'll see it when you compile the firmware from source code, or when you download the artifact from the automated build actions.