Active Topics

 


Reply
Thread Tools
Texrat's Avatar
Posts: 11,700 | Thanked: 10,045 times | Joined on Jun 2006 @ North Texas, USA
#21
it's helpful to avoid ill-formed assumptions when asking questions-- helps avoid pointless arguments.

but the answer is yes.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
 
mikec's Avatar
Posts: 1,366 | Thanked: 1,185 times | Joined on Jan 2006
#22
Originally Posted by gidoca View Post
Looking at some of the sample images (for instance this one), to me the artefacts from excessive noise reduction actually seem to be more annoying than the noise itself.
That photo looks very uncharacteristic of N900 photos taken in daylight. I noticed the directory is 08 2009, was this a very early sample?
 
Sopwith's Avatar
Posts: 337 | Thanked: 283 times | Joined on Nov 2009 @ NYC
#23
Originally Posted by Jack6428 View Post
- Increased battery life by 10%
While you're at it, why not add "extra inches" to the screen, via a firmware update...
 
skalogre's Avatar
Posts: 327 | Thanked: 249 times | Joined on Sep 2009 @ Λεμεσιανός, ρε!
#24
You know, this is rather interesting in a way, seeing all these people who have no clue about the sheer complexity of software release and maintenance getting to peek inside the process - and have a voice

Maybe there needs to be some sort of new user orientation that forces them to go through some article about the difficulty of creating and testing software before they can post a new thread complaining about the "lack of updates" or "why are there bugs in the software"
(I guess I am only half-joking).
 

The Following 5 Users Say Thank You to skalogre For This Useful Post:
Posts: 289 | Thanked: 560 times | Joined on May 2009 @ Tampere, Finland
#25
Originally Posted by skalogre View Post
You know, this is rather interesting in a way, seeing all these people who have no clue about the sheer complexity of software release and maintenance getting to peek inside the process - and have a voice

Maybe there needs to be some sort of new user orientation that forces them to go through some article about the difficulty of creating and testing software before they can post a new thread complaining about the "lack of updates" or "why are there bugs in the software"
(I guess I am only half-joking).
No, it's much easier to just ignore all that and start complaints with "There's no excuse ..."
 

The Following 2 Users Say Thank You to jsa For This Useful Post:
Posts: 53 | Thanked: 49 times | Joined on Jun 2007
#26
Originally Posted by skalogre View Post
You know, this is rather interesting in a way, seeing all these people who have no clue about the sheer complexity of software release and maintenance getting to peek inside the process - and have a voice .
I think the frustration is not without reason. Waiting suck, and long waiting suck even more. I think it is mainly caused by the monolithic release process - all or nothing. There is a release and it has certain things it should have. It there is issues with address book, the updates for browser are no-go until the address book is fixed. I understand it is one way, but I can't see it as customer friendly or efficient way to operate.

If somebody else thinks the same, please add some weight by voting up the following brainstorm: http://maemo.org/community/brainstor..._packages-002/
 
skalogre's Avatar
Posts: 327 | Thanked: 249 times | Joined on Sep 2009 @ Λεμεσιανός, ρε!
#27
Originally Posted by jsa View Post
No, it's much easier to just ignore all that and start complaints with "There's no excuse ..."


Naturally! I pity any involved Maemo team members that have as part of their job description navigating the tumultuous seas of irritated masses on the "intartoobzwebz" ! Seriously, after years in software QA I see some of these posts and immediately think "what alternate universe do these people live in?"
 

The Following User Says Thank You to skalogre For This Useful Post:
skalogre's Avatar
Posts: 327 | Thanked: 249 times | Joined on Sep 2009 @ Λεμεσιανός, ρε!
#28
Originally Posted by VRe View Post
I think the frustration is not without reason. Waiting suck, and long waiting suck even more. I think it is mainly caused by the monolithic release process - all or nothing. There is a release and it has certain things it should have. It there is issues with address book, the updates for browser are no-go until the address book is fixed. I understand it is one way, but I can't see it as customer friendly or efficient way to operate.

If somebody else thinks the same, please add some weight by voting up the following brainstorm: http://maemo.org/community/brainstor..._packages-002/
I know it may seem to be a simple issue of just updating some components and sending them out but it is a complex issue.

I agree, some updates would be nice to be released earlier (like having the hardware keyboard language switch working, for instance :-( ) but remember that this software will come packaged with the device so everything work together in concert out of the box.

Anytime you alter code that interacts through API/services/processes/et.c. you run the risk of inadvertently altering the expected input of other applications, causing them to fail or work in an undesirable way. Especially critical in a complex system like these devices that come with all this software packaged, installed and ready to go from point of sale. Legacy/regression testing is time consuming. Even solely crunching through automated testing cannot solve this (if nothing else it can give a false sense of security in some situations but that is a separate discussion ).
See: http://en.wikipedia.org/wiki/Regression_testing

Last edited by skalogre; 2009-12-05 at 22:35. Reason: Forgot an "L" - oops!
 
Posts: 53 | Thanked: 49 times | Joined on Jun 2007
#29
Originally Posted by skalogre View Post
I know it may seem to be a simple issue of just updating some components and sending them out but it is a complex issue.

I agree, some updates would be nice to be released earlier (like having the hardware keyboard language switch working, for instance :-( ) but remember that this software wil come packaged with the device so everything work together in concert out of the box.
Of course it can be complex but it is not always. Maemo is more like a Linux distribution than one single binary. If you do modify libc, you're better to test a lot of stuff as almost everything has dependencies with it. But if you fixes for two applications which are not related..

Application is ready to release - run all possible test for it and the system -> they work -> release the application. Another application is ready -> run all possible test for it and the system -> they work -> release the application. Nokia has weekly builds and I'm quite certain that some poor bastard are testing from week to week the same applications which haven't had any changes..
 
mrojas's Avatar
Posts: 733 | Thanked: 991 times | Joined on Dec 2008
#30
Maybe there should two different types of updates, one specifically aimed a bug fixing and another to add new features...

Just a raw idea, because being forced to expect a big patch to fix small annoying issues that could be fixed in little patches is going to piss off people a lot. I know is a weird comparison, but it is like having to wait for a Service Pack while a small KB fix could solve your issue; in the M$ world.
__________________
Hola! Soy un Guía de Maemo!.

Vínculos interesantes si nos visitas por primera vez (en inglés): New members say hello , New users start here, Community subforum, Beginners' wiki page, Maemo5 101, Frequently Asked Questions (FAQ)

Si te puedo ayudar con cualquier otra cosa, sólo dilo!
 

The Following 3 Users Say Thank You to mrojas For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 02:05.