QA and bibisecting in a huge software project

Transcript

1. 1 QA and bibisect
2. 2 Random comment on the Interwebz “Have you ever tried to contribute to OpenOffice? The project is infamous for basically ignoring the contributions of the non-blessed.” – Anonymous guy on the net
3. 3 Why starting at QA If you are shy about contributing, QA is a great way to get started: You interact with developers You learn how the developers work You will be more confident about contributing code on your own
4. 4 Verify a fix! Go to bugzilla Search for bugs in resolution “fixed” Get a daily build and see if the bug is indeed fixed How does this help: Commits that fix a bug are usually linked in bugzilla – so you can learn about how it was fixed Sometimes, fixing a bug creates a new one ;)
5. 5 Confirm a reported bug! Go to bugzilla Search for bugs in status “unconfirmed” How does this help: A confirmed bug can be assumed to be well-described A bug report that cannot be confirmed will lead to additional useful information collected
6. 6 Bibisecting regressions Idea: Put More than five hundred complete binary builds Into One git repository!