Reply
Thread Tools
Posts: 2 | Thanked: 1 time | Joined on Jan 2010
#191
Originally Posted by Rushmore View Post
I think it is much simpler, in that the staff responsible for Maemo 5 updates and rolling them to the N900 is probably a small team compared to an OS like Android.
I'm sure that's the case. I really like Nokia, but I can't figure out their business strategy. They seem to develop way too many phones to the point that they get overextended. There's no way to demand attention to detail from developers if they have to manage so many versions.
 
Posts: 65 | Thanked: 43 times | Joined on Dec 2009
#192
Originally Posted by fribeiro View Post
I'm sure that's the case. I really like Nokia, but I can't figure out their business strategy. They seem to develop way too many phones to the point that they get overextended. There's no way to demand attention to detail from developers if they have to manage so many versions.
I think this comes from the fact that earlier it was the "feature phones" that people wanted. This is still very much the case for example in Japan. People buy the phone because it looks cool and has some special trick. So you made lots of different kind of phones where people could select the features they wanted.

Now this has shifted to the customizable smart phone era. The phone can do anything and people install the software they want. Nokia did promise little while back that they will start making less phone models and concentrate more on the service area. Sounds good to me. I guess we will see if they succeed.
 
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#193
Originally Posted by Rushmore View Post
I think it is much simpler, in that the staff responsible for Maemo 5 updates and rolling them to the N900 is probably a small team compared to an OS like Android.
Don't really see the relevance of that to this discussion; these updates are already written, built and packaged; the effort has been spent. The objection is to Nokia not simply pushing the finished updates to the public repositories, not about how long it's taken to write them in the first place.
 
Posts: 1 | Thanked: 0 times | Joined on Jan 2010
#194
Originally Posted by Keir View Post
I just hope this'll be the one to fix the Three sim card issue.
According to the bug report it does. I'll be happy just to have that fixed

@ Ewan. You can almost guarantee that if they quickly released and there were some bugs, Nokia would be ripped to shreds by the media.

Last edited by Mattj; 2010-01-01 at 20:40.
 
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#195
As I say; everyone else manages this OK, including the 'enterprise' distributions for whom released bugs cost real money in lost confidence and effort to clear up. Maemo is not special.

Besides which, it's not like we don't have a process for this already - simply use the same approach as maemo.org does; testing versions go into the testing repo, get tested, get pushed to release when they're done. Just like (almost) everyone else does.

In any case; there are bugs in the release firmware; if the media were going to rip anyone to shreds surely they'd be as likely to do it over a stubborn refusal to allow people access to known, done, finished and working fixes for those?

Last edited by ewan; 2010-01-01 at 20:46.
 

The Following User Says Thank You to ewan For This Useful Post:
Posts: 1,255 | Thanked: 393 times | Joined on Oct 2009 @ US
#196
Originally Posted by ewan View Post
Don't really see the relevance of that to this discussion; these updates are already written, built and packaged; the effort has been spent. The objection is to Nokia not simply pushing the finished updates to the public repositories, not about how long it's taken to write them in the first place.
Well, now that you have ponted this out, where the hell is the update

Why not release if finalized and ready?
 
Jack6428's Avatar
Posts: 635 | Thanked: 282 times | Joined on Sep 2009 @ Black Mesa Research Facility
#197
If i should state the problem i have with Nokia politely, i would say this:

I wish you guys communicated more with your customers. So far, at the moment, it looks like as if you don't have much interest in us. That's not how should a giant company like you act. The birth of the N900 alone was very blurry and puzzled and not fair to the people waiting for their pre-order to arrive. Try doing better next time please. You will save yourself some bad reputation and image.

Last edited by Jack6428; 2010-01-01 at 21:01.
 
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#198
Originally Posted by Rushmore View Post
Why not release if finalized and ready?
It's not necessarily final as such; but we know it's at least ready for testing, because it's been released to a select group of testers.

My points are essentially this:

* No-one needs big monolithic firmware updates when you can do a package at a time. Test each one, then release each one.
* Testing is good; more testing is better. When you've got people jumping up and down offering to help you, let them.
 

The Following 3 Users Say Thank You to ewan For This Useful Post:
Posts: 65 | Thanked: 50 times | Joined on Dec 2009 @ Eugene, Or
#199
I would rather have a stable tested firmware released when its ready.... not before because of some arbitrary date..

ctfo people
 
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#200
OK; that's good for you. But that's not incompatible with either of the things I was suggesting, now; is it?
 
Reply

Tags
fictional update, limpware

Thread Tools

 
Forum Jump


All times are GMT. The time now is 12:51.