From The Document Foundation Wiki
Jump to navigation Jump to search

--> A successful bibisect will leave developers with only a few commits to search through to find the 'culprit' commit that we believe introduced a regression. Depending upon the particular bibisect repository, this range might be 60, 100, or even 2 commits. (We also have some very 'coarse' bibisect repositories that use released versions + beta + RC builds, and these may have ranges spanning multiple hundreds of commits) QA can go the additional step of fully bisecting (determining the exact commit) or can leave this to the developers. Often times, it's easy to find the commit that caused the issue after bibisecting the bug.