Jump to content

Edit History

Please note that revisions older than 365 days are pruned and will no longer show here
meganoth

meganoth

23 minutes ago, AllUses said:

That‘s at least confusing as experimental usually not equal to stable.

Steam shows different entries for v1.0 stable and experimental builds.

If b333 is the same as v1.0 then v1.0 was out way before been officially said as b333 was available before. Is confusion part of the game?

I hesitate to start a new map if it‘s not v1.0. Dont‘t want to restart one day later when v1.0 downloads.

 

When software is developed the developers bring out prototype versions out and test them. Whenever they find bugs or things to improve they correct them and build a new prototyp and first test if the bugs are really gone. When they finally have a prototype they are satisfied with and all bugs they tried to correct are really corrected they publish that last prototype as stable version. The important thing is that you can't just fix bugs and not test them!!

 

Therefore the last prototype is always the same as stable in software development. You just don't see that last prototype if the software is developed behind closed doors.

 

In reality there still could turn up a serious bug that needs a quick patch release even days after release. You would have to wait much longer to make absolutely sure. But I bet that they would make a big effort that any patch does not need starting a new game

 

 

 

meganoth

meganoth

11 minutes ago, AllUses said:

That‘s at least confusing as experimental usually not equal to stable.

Steam shows different entries for v1.0 stable and experimental builds.

If b333 is the same as v1.0 then v1.0 was out way before been officially said as b333 was available before. Is confusion part of the game?

I hesitate to start a new map if it‘s not v1.0. Dont‘t want to restart one day later when v1.0 downloads.

 

When software is developed the developers bring out prototype versions out and test them. Whenever they find bugs or things to improve they correct them and build a new prototyp and first test if the bugs are really gone. When they finally have a prototype they are satisfied with and all bugs they tried to correct are really corrected they publish that last prototype as stable version. The important thing is that you can't just fix bugs and not test them!!

 

Therefore the last prototype is always the same as stable in software development. You just don't see that last prototype if the software is developed behind closed doors.

 

In reality there still could turn up a serious bug that needs a quick patch release even days after release. You would have to wait much longer to make absolutely sure.

 

 

×
×
  • Create New...