Bug non verification criteria

One of goals of patch certification process is to verify the bug fixes introduced by the patch. However not every bug can be easily reproduced and verified for bug fixes. Especially when considering the limited manpower, we can not verify all bugs. This wiki page is trying to give a criteria on what kind of bugs can be bypassed without verification:

1. Bugs are not related to service and software quality, for example, bugs in ETICS building system.

2. The information provided on Savannah bug page is not enough and it's difficult for you to find more information.

3. Bugs only appear against services not in gLite release or EGEE production system.

4. Bugs only appear with some special or rare services, for example, BQS batch system. In this case, you can try to reproduce and verify it through production system at first. If it is still difficult to do, the bugs can be bypassed.

5. It needs too much of time, for example, more than one day, to reproduce the bug and verify the fix.

6. The bug fix is not verifiable.

Please notice that although some bugs are not verified, you still need to run certain tests defined by the service certification checklist to assure that the patch does not introduce new bugs and break services.

-- DiQing - 31 Oct 2008