Hello Christian,
OK, then let me just cut through the chafe.
Do I believe there is a general quality control problem with the OO.o
project - yes.
Is it overwhelming in scope - no I think not.
First though - just to break down what I think is a couple of
conversation points happening in this thread - and to address only one here.
Old issues are building up - Near the bottom of Thorsten's blog entry on
GullFoss he writes:
"Only fixing a lot of issues will costs time, but will not help in
general to make the product better for all users. "
I disagree with this opinion, for this reason.
Start with the following assumptions on my part:
There are very few pieces of code in a modern application that can be
reached by only one path of execution, in fact, it can be near
impossible, in some cases, to say with any reasonable degree of
certainty that all paths can be documented.
Experience shows that adding new functionality to existing code lines
runs a higher risk of delivering more serious bugs then all new code.
("delivering" I mean- delivering to users) ("adding to" here is meant to
include such things as 'adding extensions' that make heavy use of
existing API's)
That the greater the number of un-resolved issues in that existing code
line the higher that risk.
This is far from the only reason of course, but IMO, one reason and
directly pertinent here.
So - Do I think the number of old issues currently unresolved is a
problem that should be vigorously addressed? Yes.
There is, IMO, a big role for the QA to play here, one that external QA
volunteers can certainly participate in. That is taking that 'big pile'
and cleaning it out of those issues that are no longer valid. Then
taking a hard look at what is left, along with folks from Dev, UX, etc.
(I'll just pop this in again - quarterly reviews) and biting the bullet
to say...ok, this needs to be fixed - ahead of 'new' work! (and of
course the other option also - that some just won't be fixed, for
whatever reason - that's just a reality)
That's my thoughts on that question anyway - if you find any agreement
in those thoughts then the question should shift to how we can make a
run at that 'big pile' in some concerted way.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
