That's not an odd approach at all. As someone already stated, that's not how development works. What may seem to you as a week or two delay is not the same type of delay that is seen on the development side. It takes many processes that rely on one another to complete a formal release of software. You have development, Dry Runs, SCM, Quality, SQA, FQT not to mention budgets, schedules and cost effectiveness of the entire process. It's not just as simple as fixing a line of code and sending it out for release. One single word, line or modification can have a negative impact on code that was already working.
Originally Posted by Dvigilante1
For example, if a bug is found during FQT (Formal Quality Tests), which is one of the last technical aspects of a formal release (however, many administrative aspects remain) a decision must be made. What type of impact will this bug have on the OS as a whole? According to the plan that is already in place, does fixing it now have any added value?
So they say lets fix it now:
-Fix it now (which means that the software must be sent back to development, the developer must reproduce the issue and find a solution for it). While this is taking place, time-lines are shifted, schedules are pushed out, cost effectiveness is again reevaluated and many more things happen that must be taken into account. So after the solution is found and implemented, the entire process begins once again. Dry runs of the software begin once again, Quality begins to take a look at it. SCM logs the current iteration into their systems. FQT is scheduled, SQA must show up and verify the testing once again. All this takes money and manpower and it must be done with cost effectiveness always in the forefront.
Yes, HP can assign 10,000 engineers to do this but is that really cost effective? Absolutely not. HP is more than just WebOS.
-Decide that the bug is a minor one (fix it later with an update):
This allows for testing to continue, the plan in place continues to meet their milestones. Schedules/Paths are on the continued track. I could continue to list many of the systems/process that happen but I know it's getting boring. Lol
Needless to say, it's very large process that happens behind the scenes. Finally, lets not forget that HP is a publicly traded company and they have shareholders that request answers for their questions. Shareholders just add to fuel to the volatile but controllable fire.
Homebrew doesn't need to go through all this. They take the already finished product and modify it to their liking. That's one of the beauties of WebOS. HP doesn't discourage this practice. They encourage it.
Hope this helps clear things up you.