![]() |
Re: Has anyone from the Maemo team actually responded to any bugs?
it's helpful to avoid ill-formed assumptions when asking questions-- helps avoid pointless arguments.
but the answer is yes. |
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
|
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
:rolleyes: |
Re: Has anyone from the Maemo team actually responded to any bugs?
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 :eek:
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). |
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
|
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
If somebody else thinks the same, please add some weight by voting up the following brainstorm: http://maemo.org/community/brainstor..._packages-002/ |
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
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" :D ! Seriously, after years in software QA I see some of these posts and immediately think "what alternate universe do these people live in?" |
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
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 |
Re: Has anyone from the Maemo team actually responded to any bugs?
Quote:
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.. |
Re: Has anyone from the Maemo team actually responded to any bugs?
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. |
All times are GMT. The time now is 21:33. |
vBulletin® Version 3.8.8