Why skip to 4.2.1 when 4.2 wasn't released.
Note: I don't work for Apple, this is just a possible explanation:
Many companies have tied process to versioning. In other words a bug fix that requires a rebuild of one component may not necessitate a full retest of the component. Thus you can have 4.2GM, 4.2GM+fix.
If the fix is deep enough that it causes a sufficient change to reopen testing or to regression test (did this fix break anything already working) they may need to increment the version number to match documented process.
Thus:
-Andrei Freeman
(Who recently went to the street initially with a 1.0.1, not 1.0)
I am really glad to see they are trying to iron out as many kinks as possible before releasing this. I'm a little curious why they chose to go to 4.2.1 and not just keep it at 4.2 with a different build number.
Can someone wiser than me tell me why they would add a .1 before the general release of .0?
Note: I don't work for Apple, this is just a possible explanation:
Many companies have tied process to versioning. In other words a bug fix that requires a rebuild of one component may not necessitate a full retest of the component. Thus you can have 4.2GM, 4.2GM+fix.
If the fix is deep enough that it causes a sufficient change to reopen testing or to regression test (did this fix break anything already working) they may need to increment the version number to match documented process.
Thus:
- 4.2 Beta: Apple Q/A testing
- 4.2 GM: Official Q/A testing is done, ad hoc widespread testing and distributed dev testing
- critical wifi bug that affects just the iPad discovered
- 4.2 GM+iPadFix (test only that fix as the code change was minor despite the bug being critical)
- critical bug discovered via adhoc (maybe a 3rd party dev) that requires a fix to the entire release.
- 4.2.1 beta (unreleased/unannounced/unleaked): Apple Q/A testing
- 4.2.1 GM: As above.
-Andrei Freeman
(Who recently went to the street initially with a 1.0.1, not 1.0)