Since I haven’t seen anyone post this, I thought I’d share the new Star Engine demo video from Cloud Imperium Games.
Conventional version numbering (afaik) lead up to 1.0 as the release candidate.
Usually yes if you use only numbers, but when you use alpha/beta/release cycles etc, it’s not that uncommon to have them start from 1.0 as well.
As an example, the fifth phase of minecraft dev started with “Minecraft Alpha v1.0.0” and once it got to v1.2.6, the next was “Minecraft Beta v1.0.0”. The proper Minecraft 1.0 came after Beta 1.8.1.
That was a standard that existed because of older, ‘linear’ SDLCs. It stopped being the case when Agile development took over. When you’re using Waterfall, and all your milestones are planned out before a single line of code is written, you can do that.
Modern software development doesn’t work like that, and it’s silly to use nth-degree nested decimals (0.1.0, 0.1.1.2) when you can just use 1.1, 2.13, etc, and call something RC1.0 and 1.0 on release without bothering with internal version numbers or project codenames (or just keep the working version numbers anyways).
