- Dec 17, 2017
- 7,426
- 9,701
You're this out of context. Drill back a few responses. I wrote
Someone wrote
I responded:
and then someone else wrote
- May 21, 2018
- 165
- 310
I'm not taking it out of context. I read the whole thing. Version 1.0 means (or rather should mean) it's finished. It's just a bunch of idiot developers who think it uses the decimal system use 1.0 to follow 0.9 while it should be 0.10. Still doesn't mean it's right.
- Dec 17, 2017
- 7,426
- 9,701
That's incorrect. Even with the semantic versioning spec, 1.0 is not done. In semantic versioning, 1.0 defines the public API.
Sometimes 1.0 means it is finished. Sometimes 1.0 does not mean it is finished.
Sometimes 1.0 comes after 0.9. And sometimes 0.10 comes after 0.9.
There is no hard and fast standard, and no requirements to do anything.
- Oct 12, 2018
- 1,234
- 454
- Mar 28, 2017
- 12,296
- 16,908
I'm just gonna name the next version "V@.
.-1" now.
.-1" now.You can check my previous posts to find it. It's within this thread though.
- Sep 6, 2017
- 761
- 307
- Dec 17, 2017
- 7,426
- 9,701
That's correct.
It might be possible to load the game into the SDK on a Mac or PC, then load it on an ipad using developer credentials, but I have no idea how that actually works.
- May 20, 2017
- 20
- 11
Almost correct. In semantic versioning 1.0.0 is the version number of the first stable (ready to production use) release, _and_ defines the public API too.
There are more than one versioning system in use (
You must be registered to see the links
), and of course you can create your own system if you wish. Unfortunately there is no standard for it.The worst thing is that some developers too lazy (or careless) to find a well-known system which suits for their development strategy, and it can cause misunderstandings. I'm always mad when I download something with 1.x version number, and I have to realize that it was just an alpha version with tons of bugs, and lack of content.
- Nov 14, 2018
- 284
- 364
There is no standard for version number, but you should do it in a way that makes sense to you and contains all the information you may need to track that build. I worked for a company that essentially broke it down like this:
[Major build number].[Minor build number].[Revision].[Package]
i.e. Version: 1.0.15.2
Even though the categories are defined, there's still ambiguity for what kind of features actually cross over between a revision and a minor build number. It's up to you. If you make lists of the features that will need to be implemented before each increment, you'll also have a plan to follow, but in the end it's your decision as to what fits into each category.
/copy pasted from stack overflow/
[Major build number].[Minor build number].[Revision].[Package]
i.e. Version: 1.0.15.2
- Major build number: This indicates a major milestone in the game, increment this when going from beta to release, from release to major updates.
- Minor build number: Used for feature updates, large bug fixes etc.
- Revision: Minor alterations on existing features, small bug fixes, etc.
- Package: Your code stays the same, external library changes or asset file update.
Even though the categories are defined, there's still ambiguity for what kind of features actually cross over between a revision and a minor build number. It's up to you. If you make lists of the features that will need to be implemented before each increment, you'll also have a plan to follow, but in the end it's your decision as to what fits into each category.
/copy pasted from stack overflow/
- Nov 14, 2018
- 284
- 364
- Mar 28, 2017
- 12,296
- 16,908
March will be the month of sisters
Sam in F.I.L.F.
Caroline in Milfy City
boths sisters in Midnight Paradies
Jenny in Summertime SagaMarch will be the month of sisters
Sam in F.I.L.F.
Caroline in Milfy City
boths sisters in Midnight Paradies
Question is if all these will release in March.