I ?m on 4.0.2 stock GNEX. I would love to have an update, but I have no major issues with the phone. I have also managed developers of a large business critical mainframe system that is used globally ? all parts of the world. Our schedule was that we would do releases (enhancements and fixes) 3 times a year-- if we could.
It?s not like all you have to do is change a few lines of code and you?re done.
First you have to identify what is causing the problem, or what needs to be done to provide an enhancement. Then you need to determine how/if you can satisfy the requirement given the existing hardware and software you have. Next you have to consider the ramifications to the system?.will something else break? If you can?t fix that area so it works with the existing system and other changes?.suddenly one change may become 12.
After coding unit testing takes place?finally it works.
After unit testing system testing takes place ? All changes by all developers are incorporated into a test operating system. It gets tested by the developers. Something is broken?....It needs to be fixed.
Next stakeholder testing takes place(CDMA Verizon, AT&T are stakeholders) Something is broken it needs to be fixed.
Stakeholder retesting takes place sometime on their schedule.
In some cases fixes don?t make the final cut because they need further tweaking.
Finally we have a system that can be released for production usage. Then we repeat this process for the next upgrade.
The scenario I described was for a system using the same hardware and software?imagine the mess you have when you are using different hardware and communication methods.
I would love to have an upgrade but I know It is not taking place in 2 or 3 months?more like 4 to 6.
4.05 may be 4.04 with CDMA communication and Verizon LTE binaries being the difference.
It?s not like all you have to do is change a few lines of code and you?re done.
First you have to identify what is causing the problem, or what needs to be done to provide an enhancement. Then you need to determine how/if you can satisfy the requirement given the existing hardware and software you have. Next you have to consider the ramifications to the system?.will something else break? If you can?t fix that area so it works with the existing system and other changes?.suddenly one change may become 12.
After coding unit testing takes place?finally it works.
After unit testing system testing takes place ? All changes by all developers are incorporated into a test operating system. It gets tested by the developers. Something is broken?....It needs to be fixed.
Next stakeholder testing takes place(CDMA Verizon, AT&T are stakeholders) Something is broken it needs to be fixed.
Stakeholder retesting takes place sometime on their schedule.
In some cases fixes don?t make the final cut because they need further tweaking.
Finally we have a system that can be released for production usage. Then we repeat this process for the next upgrade.
The scenario I described was for a system using the same hardware and software?imagine the mess you have when you are using different hardware and communication methods.
I would love to have an upgrade but I know It is not taking place in 2 or 3 months?more like 4 to 6.
4.05 may be 4.04 with CDMA communication and Verizon LTE binaries being the difference.