[chief1983]

Nope, I was replying to the post before yours before you posted yours.

[Goober5000]

At work we use Major.Minor.Patch.State.Build
...
Perhaps the SCP could do something similar?

SCP does something very similar.  To use your notation, we say 3.Major.Minor.Build.

[Tomo]

At work we use Major.Minor.Patch.State.Build
...
Perhaps the SCP could do something similar?

SCP does something very similar.  To use your notation, we say 3.Major.Minor.Build.

Indeed - I'm suggesting inserting a "Status" in between Minor and Build/Revision.
Status could be "0" for "Nightly Build", then 1 thru 8 for RCs and finally 9 on the frabjous day.

[General Battuta]

That scares me a little, people already find the terminology a little intimidating. If a number changes it should be the last number in the string so people always know to grab the one with the biggest number!

[chief1983]

Batty, it still leads to a bigger number overall...

[General Battuta]

As long as you're not including the revision number on the end, yeah, but I just want to avoid situations where people get hung up on a long string of digits and their eyes glaze over. People are very prone to transposing and dropping digits in strings, so the more values in the string the more dangerous it is - people start swapping their 3.6.16.9s with their 3.6.9s and dumb stuff like that.

[The E]

I would agree that 3 significant numbers is quite enough for us. Anything more, and it gets rather silly.

[niffiwan]

I think I'd prefer not to use 3.6.17, as that's already used in the BP builds and it'd be nice to have the fs2_open.log clearly distinguish between pre-3.7.0 and BP.

[chief1983]

Isn't that because it was already committed to antipodes that way? 

[niffiwan]

Yes, antipodes is currently 3.6.17  (forgot about that )