Joe Belfiore, Director of Windows Phone Program, recently gave a video interview discussing the NoDo Update process ( video and response embedded after the break ) where he mentioned how the process actually works or doesn't work - depends if you have NoDo or not. He mentioned how they have this throttling approach where they push the update to limited number of phones i.e they are basically sending the update in phases.
In layman terms, he mentioned how they have this throttling approach where they push the update to limited number of phones i.e they are basically sending the update in phases.
The update process has three phases :
What actually caused so much outrage is the fact that Joe didn't do the right thing. First he didn't accept the fact that Microsoft screwed up real bad and secondly, he stated that february update has reached most of the users which is also untrue.
But Joe responded today via a commenter on Channel 9's comment section today after reading several furious and frustated user comments, here is the complete response :
via @winrumors
Not ready for the interview? Nice try, Joe. But definitely step in the right direction since people are looking for news that makes actual progress from typical statement issues by both operators and Microsoft. So is it good enough ? Heck no. We need more transparency. I still don't have my NoDo update and I am consequently frustated. The cure ? Give me the goddamn update, Microsoft !
Have you received your NoDo update ? What do you think Microsoft is doing wrong here ? Do they have absolutely no interaction with carriers who are still testing it ? Do you think carriers are deliberately delaying the update ? Who's fault is this ? Drop in your views.
In layman terms, he mentioned how they have this throttling approach where they push the update to limited number of phones i.e they are basically sending the update in phases.
The update process has three phases :
- Testing : This is the stage where operator tests the update for any network and quality issues. Thankfully, most of the operators have gone past this stage and at the same time there are a few who are still stuck in the testing stage. I fail to understand why it is taking so long. Operators are blaming Microsoft for the update fiasco and vice versa.
- Scheduling - Once the update has passed the testing stage, Microsoft schedules the update for delivery. It takes < 10 days.
- Delivering update - Then the ' throttled ' update is pushed to the users . According to the Windows Phone Update resource, it can take several weeks to receive the update notification which is ridiculous.
What actually caused so much outrage is the fact that Joe didn't do the right thing. First he didn't accept the fact that Microsoft screwed up real bad and secondly, he stated that february update has reached most of the users which is also untrue.
But Joe responded today via a commenter on Channel 9's comment section today after reading several furious and frustated user comments, here is the complete response :
Many of you are making critical comments here which are certainly fair. First, I was wrong when I said “most people have received the February update.” There are many of you who have yet to receive it, and I don’t blame you for speaking up and pointing out my mistake. Second, I referred to our updates as “complete” because I was thinking of the internal process where we pass completed software to another group who delivers them – but of course no update is complete until you all have it. Plus, at the time I did the interview we had started the NoDo (“march update”) delivery process and I knew “it was going well” from our perspective: people were officially getting it, the success rate of its deployment on real-world phones was looking good, and we were happy that the process had STARTED well. Still—these are NOT the same as all of you getting it and I’m sorry that I came across as insensitive to that fact.
I am a very, very big advocate for all our end-users and developers, and it bothers me a lot if I sounded out of touch. I wasn’t as prepared for this interview as I should have been—I walked into the studio with an informal state of mind, thinking about MIX and what we WILL be talking about, and I didn’t have the right up-to-date information to give a good explanation on updates which I know to be a very high-interest topic right now.
I have read all of the comments here (and many of them on the other blogs) and so has pretty much everyone in our management team. We know it’s been frustrating to wait for features/fixes and (probably worse) to hear little from us on specific dates. We are sorry the process has been rocky. The “where’s my phone update” table is our first step to try to remedy this in the face of technical problems that have made our first wave of updates take longer than we expected. We know the table would benefit greatly from more detail, and we are hoping to add more to it by working with the Operators who own the “testing” phase to get more clarity. If your phone is shown in “scheduling”, it’ll be worth checking the table next week.
In the spirit of “MIX as a conversation” – I will make sure that when I show up in Vegas that I’m well prepared to give an update in person and to try to answer your questions as best I can. You folks are obviously a very important audience for us and it’s right for you to expect us to communicate and execute better. I know at this point it’s our actions that matter… The main thing we are trying to do is to get the updates out to everyone in a way that is reliable and works, and then make our process better and more transparent in the future.
via @winrumors
Not ready for the interview? Nice try, Joe. But definitely step in the right direction since people are looking for news that makes actual progress from typical statement issues by both operators and Microsoft. So is it good enough ? Heck no. We need more transparency. I still don't have my NoDo update and I am consequently frustated. The cure ? Give me the goddamn update, Microsoft !
Have you received your NoDo update ? What do you think Microsoft is doing wrong here ? Do they have absolutely no interaction with carriers who are still testing it ? Do you think carriers are deliberately delaying the update ? Who's fault is this ? Drop in your views.
