Hi Andre, Andre Schnabel wrote: > Hi Peter, > > Peter Junge schrieb: >> Hi Wolfgang, >> >> you should do the following this to get better results of bug writing. >> First of all you should apply for QA membership. When being a QA member >> the issues you write do not have the initial status 'unconfirmed' but >> 'new'. This spares the step of a current QA member confirming the issue. >> Due to the large number of bugs reported this can take quite a while. >> Another useful thing you can do being a QA member is to adjust the >> target milestone of an issue. After submitting a bug you can re-edit the >> issue to do so. The 'target milestone' property is not available for the >> initial report on an issue. >> > > please do *not* adjust the target milestone as long as you have some > developer at hand, who takes care that the target could be met. >
I have to disagree on that. In bug handling there are two flags that drive development work flow. That are Priority and Target. If Priority is low or no target available, it's hardly to imagine that the problem will be fixed. Sorry, but your statement sounds like admitting that the bug handling process of OOo doesn't work. If people join the OOo QA they should actively drive the processes by putting an issue in a proper state. If they make mistakes in the beginning that's quite normal and I am sure there will be OOo seniors to guide and educate them to improve their contribution. Having worked more than five years for StarOffice QA I am convinced that Hamburg based engineers will at least take care about issues with target milestones because all their process depend on proper targets. Best regards Peter -- Peter Junge, peterjunge(at)ch2000.com.cn Senior Engineer, Open Source Technology Beijing Redflag CH2000 Software Co., Ltd. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
