A funny thought

[Sokar408]

I just had a funny thought. Given that the patches keep increasing the patch index number by one, and assuming that the developers has a master plan that says they have to get to 1.0.0 that way, then we got .78 patches left before full release. With an average release time of 1 patch pr 2 months (assuming my hasty scroll on the patch release site is correct), that means in: 78 * 2 / 12 = 13 years we'll finally have 1.0.0

i wonder what the expansions will bring ...

[blizzy78]

This topic is new.

http://forum.kerbalspaceprogram.com/threads/25123-Game-only-19-done

http://forum.kerbalspaceprogram.com/threads/54755-Thirteen-years

[Aladran]

Same thought when we were at the 0.9 version

ppl said OMG 1.0 is next!

NOT!

0.10 was next

[Sirrobert]

Yea.... no

[Vanamonde]

Gentlefolk, please keep in mind that not everyone is familiar with the history of previous discussions, and that other games are off-topic for the KSP forum.

[NASAFanboy]

KSP 1.0 is coming out in 2027?

Meh, I can imagine the astronauts of the future playing KSP 1.0 in an base on the moon as it comes out, while complaint that the internet loads so slow.

[fatfluffycat]

They can skip numbers you know, lets say the game is 0.80, and is 99% ready for 1.0, they can skip to 0.90

Right?

[Starwhip]

Yes. It is up to the developers to say what version it is. It's all arbitrary, anyway.

[allmappedout]

As others have pointed out, it doesn't work how people think it works, but it definitely is not arbitrary. Software version control is a very important thing.

As I understand it:

a.xx.yy.zz

a = Full Version Release

xx = updates containing changes which are significant

yy = changes which are patches or fixes

zz = usually for release candidates or different builds

But it's better explained by Wiki, as usual:

http://en.wikipedia.org/wiki/Software_versioning

These threads do keep popping up though. It might be worthy of a sticky of some sort.

[Sirrobert]

As others have pointed out, it doesn't work how people think it works, but it definitely is not arbitrary. Software version control is a very important thing.

As I understand it:

a.xx.yy.zz

a = Full Version Release

xx = updates containing changes which are significant

yy = changes which are patches or fixes

zz = usually for release candidates or different builds

But it's better explained by Wiki, as usual:

http://en.wikipedia.org/wiki/Software_versioning

These threads do keep popping up though. It might be worthy of a sticky of some sort.

They can even do a.xxxxxxx.yy.zz

If they choise to

[Umlüx]

they can go like 0.22, 0.23, 1.0

or 0.98, 0.99, 0.100, 0.101 .....

they can even never go 1.0 and stay in beta forever, who knows

[Goldham]

KSP 1.0 is coming out in 2027?

Meh, I can imagine the astronauts of the future playing KSP 1.0 in an base on the moon as it comes out, while complaint that the internet loads so slow.

Or better yet future astronauts being trained using KSP

[ZedNova]

1.0 is just the version number for when squad thinks it's finished. Although it could still receive minor updates after that.

[Skyrunner27]

Same thought when we were at the 0.9 version

ppl said OMG 1.0 is next!

NOT!

0.10 was next

I think you may be miss guided. It was version .09 not .9 using that some thing we would have two versions .1

[Luckless]

Something to keep in mind about version number systems: They don't always stay totally consistent.

I've been on a project that started with a standard aa.bb.cc.dd pattern, and ended with an aaa.bbb.ccc-x in alphanumeric format.

[Kinglet]

KSP 1.0 is coming out in 2027?

Meh, I can imagine the astronauts of the future playing KSP 1.0 in an base on the moon as it comes out, while complaint that the internet loads so slow.

Ksp will be DRM?

[DevoidLight]

Version numbers aren't decimals.

[relin]

I think you may be miss guided. It was version .09 not .9 using that some thing we would have two versions .1

v0.1 is not the same as v0.10, in most cases. The company I work for treats them as separate versions, even though they're the same mathematically.

[blizzy78]

v0.1 is not the same as v0.10, in most cases. The company I work for treats them as separate versions, even though they're the same mathematically.

That's because they're just simple counters between the dots.