Hi, On 2012-02-15 at 20:13 +0100, Bjoern Michaelsen wrote:
> I added a bibisecting Howto to the wiki, please try getting started with > bibisecting and report back if you are missing information on how to proceed. > And remember: Bibisecting a bug will make it much more likely that your bug > will be fixed quickly as a bibisected regression is much easier to work out. > > https://wiki.documentfoundation.org/index.php?title=QA/HowToBibisect There was no response on this mail, so maybe the people do not understand how wonderful thing this is ;-) So let me explain: bibisect is an extremely valuable tool to find regressions. Using this, you can point the developer to _exactly_ when the regression happened, which consequently means that the developer will be able to fix the bug much faster, and much more effectively. This 'bibisecting' can be done by anyone, even by people with no hacking skills - so please, if you have a "favorite" regression in LibreOffice, try bibisect, and point us (developers) to when it happened - I am sure the bug will get much more attention than without that :-) All the best, Kendy _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/