Hello,

After this has been answered with the ususal "sorry, you need to understand, that software is never bug-free and we have limited ressources ..." some project members expressed that they are not satisfied with this situation and the everlasting excuses. In fact, I am one of those members.

me too. I have had that feeling for years.

To summarize it: A freshly reported bug is either fixed more or less immediately or it will quickly get out of focus and never be fixed; additionally even excessive number of reports of the same problem will be just booked as duplicates, but the assignment 'OOO_Later' etc. will not be changed anymore. Also I feel 'votes' are generally more or less ignored.

mine is different: The OOo project has a quality issue.

Full Ack.

Comments are welcome :)

Ok, some thoughts:

I don't know how Sun's StarOffice development teams are organized, but in the company I work for we once had a problem; our developers have been too busy with fixing bugs so that promised deadlines for new features could not be met. The solution was to have completely independent teams for development of new features on one hand and for bugfixing on the other.

The problem here is vice versa, (in my opinion) a focus on unneeded 'creeping featurism' and (sorry guys, but that's my gut feeling) a missing interest to get a 'rock-solid' and bug-free application. However, I feel one step for a solution could be the same: Establish two different development teams at Sun, where one is working exclusively on bugfixes. The teams can be rotated from time to time, when developers are not satisfied with just having to do fixes.

Secondly, I feel the importance, priority and order of fixing of general bugs should be exclusively decided by QA and/or community and not by development (I've got the feeling that right now, the latter take the decision; correct me if I'm wrong).

Regards

Guido

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to