SaturdayI think
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
2.1 ESE53 will be Official Release on the VZW Motorola Droid
- Thread starter cereal killer
- Start date
- Status
diverbelow
Member
See, in the time it took you to type that you could have just said the time.. some people make no sense..
unknowndroid
Member
To those who are already complaining about the staged roll out, here is some insight. I am an IT Project Manager and worked for Verizon from 1998 (when it was GTE) to 2007. Typically, all releases are done this way. The first group we would normally call our Production Pilot. Then we had our Post Pilot (the 9,000) and then our Production Mass (the 200,000 per day). Some of the reasons for this strategy have already been discussed, but there are others. I'll combine them here.
* If there is a problem with the update itself, as mentioned, it's better to impact 1,000 people than 1-2 million. Problems with the update can include an issue with the update package, but can also include an issue of the package getting corrupted during the actual transmission. It is rare, but it has been known to happen.
* Network bandwidth issues are possible, especially if the package does something funky during deploy and gets hung. Again, rare, but it has happened.
* For any deployment at Verizon (at least in IT), there is a project team that consists of Network engineers, software engineers, hardware engineers, support (include the help desk, and 2nd, 3rd and sometimes 4th level support). The members of this team and their management ALL need to agree on the rollout schedule. There is typically a lot of negotiation that goes on here. Some groups are OK with going faster, some slower. The Help Desk typically gets the brunt of the impact, so they usually drive the final timeline. The delay between the first day and the first day of mass is not only to make sure that people's phone's haven't blown up, but also to make sure that there is time for support to update documentation, communications, etc. As an example on the 2.0.1 update, you had to delete a few of the icons (i think Gallery was one) from your home screen and then add back on home screen. It's a lot better for Verizon to find this out with the calls they get from the first 1000 and have time to update their documentation than to have 200,000 potential callers and not have the answer yet. That way when people call, the call is seconds and not hours.
Now some people will say (and trust me, I heard it a lot internally) that support should just staff up appropriately. What most fail to consider is that this Droid update is just one of any number of possible update that could be going out today. There were times when we were massing one update and also in production pilot with another. Then there are other, non-phone specific things happening. New PRL's being deployed and lots of other stuff. The methodology used is a wise one that aims to limit impact to thee customer most of all.
Now, trust me, I'm not a Verizon apologist. I don't work there anymore for a reason. However, the methodology used for deployments is not that reason. This methodology is pretty standard in IT, no matter where you go. Sometimes, you aren't even aware of it if it is a silent update (depending on the industry).
Anyhow, it's after noon. Hoping some lucky contestant was chosen for the Production Pilot
* If there is a problem with the update itself, as mentioned, it's better to impact 1,000 people than 1-2 million. Problems with the update can include an issue with the update package, but can also include an issue of the package getting corrupted during the actual transmission. It is rare, but it has been known to happen.
* Network bandwidth issues are possible, especially if the package does something funky during deploy and gets hung. Again, rare, but it has happened.
* For any deployment at Verizon (at least in IT), there is a project team that consists of Network engineers, software engineers, hardware engineers, support (include the help desk, and 2nd, 3rd and sometimes 4th level support). The members of this team and their management ALL need to agree on the rollout schedule. There is typically a lot of negotiation that goes on here. Some groups are OK with going faster, some slower. The Help Desk typically gets the brunt of the impact, so they usually drive the final timeline. The delay between the first day and the first day of mass is not only to make sure that people's phone's haven't blown up, but also to make sure that there is time for support to update documentation, communications, etc. As an example on the 2.0.1 update, you had to delete a few of the icons (i think Gallery was one) from your home screen and then add back on home screen. It's a lot better for Verizon to find this out with the calls they get from the first 1000 and have time to update their documentation than to have 200,000 potential callers and not have the answer yet. That way when people call, the call is seconds and not hours.
Now some people will say (and trust me, I heard it a lot internally) that support should just staff up appropriately. What most fail to consider is that this Droid update is just one of any number of possible update that could be going out today. There were times when we were massing one update and also in production pilot with another. Then there are other, non-phone specific things happening. New PRL's being deployed and lots of other stuff. The methodology used is a wise one that aims to limit impact to thee customer most of all.
Now, trust me, I'm not a Verizon apologist. I don't work there anymore for a reason. However, the methodology used for deployments is not that reason. This methodology is pretty standard in IT, no matter where you go. Sometimes, you aren't even aware of it if it is a silent update (depending on the industry).
Anyhow, it's after noon. Hoping some lucky contestant was chosen for the Production Pilot
But look at all the time you wasted reprimanding when you could of just told him, geeze
LethalInjection
Member
^^^
Lol
There will eventually be someone on here freaking out, OMG I GOT IT!#@@$#%#%!@%#
If so a little quick review would be nice
Lol
There will eventually be someone on here freaking out, OMG I GOT IT!#@@$#%#%!@%#
If so a little quick review would be nice
No, they are still in Motorola warehouses.The 1000 phones that got it are all probably sitting on display shelves at verizon stores..
- Status
