Hi Max,
Maximilian Odendahl schrieb:
Hi,
The problem is a bit more complex. The testers and test script writers
do not have any time for writing new test cases for new functionality,
they do not have time to check fixed issues in master, they do not have
time to check code changes in a CWS as much as they should
Maybe it is an idea to change the resolved fixed - verified process? It
is a waste of time in about 99% of all case probably. The developer
tests the issue before handing over the CWS and then sets it to
Resolved, so there is a pretty small chance that the issue itself is not
really fixed. And remember, it will be again checked for setting the
issue to closed anyway.
Do you know, how often a CWS returns back to development because of
broken functionality, not fixed issues or process violation? Its
up to 25-30% of all CWSs. You can check this in EIS. The data is
stable over the past years. :-(
Therefore in my opinion it isn't good to change the handling of
'resolved/fixed'->'verified' status.
But to check the issues in Master => verified -> closed could be
discussed. Here the numbers are really 99% I think. Nearly all
issues which are fixed in CWS are fixed in Master too.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
