This is a QA easyhack. We are currently creating a tool, which allows us to do a bisect graphically.
Anyhow, we need to ensure that it is working.
A short (really short) guide how to set this up can be found here: https://github.com/reisi007/Bibi-GUI#bibi-gui
A pre-release version can be found at: http://florei-libo.115.at/QA/monoBibiGUI/
If the location changes, I will announce that in the comments.
How to verify the algorithm?
1) Pick a bug, which you want to bisect.
2a) Bisect the bug with git: https://wiki.documentfoundation.org/QA/HowToBibisect
2b) Bisect the bug with my program
3) Check that the result (should be same information)
If you need any information, use this mailinglist: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
PLEASE subscribe before posting to this mailinglist
New location: http://dev-builds.libreoffice.org/.bibi-gui/GitBisectGUI.zip
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
see also: https://redmine.documentfoundation.org/issues/633
Im merging this with here for now although the other task was, quote:
We really want one that's cross-platform (Joel)
Can be pretty simple -- just 3 buttons
Maybe focus on GNU/Linux for now, as that's looking like most of our bibisect area
If the current bibisect UI cant be made crossplatform easily, it need a rewrite from scratch. Then that should be split out of this issue in a separate issue.
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, topicQA)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
Not my scope
git libraries are still to slow, there won't be a BiBi GUI anytime soon (sadly)...