Hands-On: Google Nexus 4
4.1/4.2 nomenclature
Forgive my ignorance, but what is the difference between 4.1 and 4.2, and why are they called the same thing? Before I read this article, I didn't even know of 4.2, and I thought that it would be called Key Lime Pie (or something beginning with 'k'). When did this all play out?
Thanks.
Thanks.
...
From what I've seen of 4.2, it seems like what Jellybean should have been when it came out.
4.1 only included mostly speed improvements (aka project butter) and the initial releases of some features like Google Now, and enhanced notifications.
It's likely that some of the features weren't ready when Google wanted to release Jellybean by, so they were pushed back until now.
Also, Google wants to only release new major versions (as in new codename) on a yearly cycle.
4.1 only included mostly speed improvements (aka project butter) and the initial releases of some features like Google Now, and enhanced notifications.
It's likely that some of the features weren't ready when Google wanted to release Jellybean by, so they were pushed back until now.
Also, Google wants to only release new major versions (as in new codename) on a yearly cycle.
...
Only the big releases get code names....this is just a small update, fixing minor bugs and so forth.....it doesn't introduce signfiicant new features or change the UI in any significant way
...
Any idea why they would label this update 4.2, instead of say 4.1.1 like many of the other minor updates?
Seems like 4.2 should have been reserved for KLP, unless they're jumping up to v5 for the next major release....?
Not that it really matters, I'm just curious as to the logic there.
Seems like 4.2 should have been reserved for KLP, unless they're jumping up to v5 for the next major release....?
Not that it really matters, I'm just curious as to the logic there.
...
I suspect that Key Lime Pie (or whatever they decide to call it, I can't think of any other dessert dish that starts with K) will be version 5.0...
It just makes sense for the big 'code named' releases to be the x.0 releases.
But they actually already have 4.1.1, the most recent update was 4.1.2, so this would really have to be 4.1.3.
There is no hard and fast rule for how to number things, but basically the way companies tend to do it is that if there is a significant UI change, then it moves up to the next number, say 2.0 to 3.0, if it is only minor bug fixes that don't introduce significant new features then you increase the third number, so it goes from, say, 3.0 to 3.0.1, and if there are changes more significant enough for the...
(continues)
It just makes sense for the big 'code named' releases to be the x.0 releases.
But they actually already have 4.1.1, the most recent update was 4.1.2, so this would really have to be 4.1.3.
There is no hard and fast rule for how to number things, but basically the way companies tend to do it is that if there is a significant UI change, then it moves up to the next number, say 2.0 to 3.0, if it is only minor bug fixes that don't introduce significant new features then you increase the third number, so it goes from, say, 3.0 to 3.0.1, and if there are changes more significant enough for the...
(continues)
...
This forum is closed.
