You can browse the source code for the development focus branch or get a copy of the branch using the command:
bzr branch lp:bzr-bisect

Bazaar Bisect Plugin has 2 active reviews. See all merge proposals.

Bazaar Bisect Plugin has 3 active branches owned by 2 people and 1 team. There were 0 commits in the last month.

Bazaar branches

Name Status Last Modified Last Commit
Series: trunk
bug 2 Mature 2012-08-03 13:03:48 UTC
84. Merge fix for compatibility with newe...

Author: Jelmer Vernooij
Revision Date: 2012-08-03 13:03:48 UTC

Merge fix for compatibility with newer versions of bzr from Thomi.

lp:~naesten/bzr-bisect/683822-bisect-start-range-argument bug(Has a merge proposal) 1 Development 2012-09-21 21:46:07 UTC
91. Add some debug output (mostly log-only).

Author: Samuel Bronson
Revision Date: 2012-09-21 21:46:07 UTC

Add some debug output (mostly log-only).

lp:~jeff-licquia/bzr-bisect/yesno bug(Has a merge proposal) 1 Development 2012-09-16 15:15:56 UTC
85. Don't hardcode the association betwee...

Author: Jeff Licquia
Revision Date: 2012-09-16 15:07:10 UTC

Don't hardcode the association between "yes" and "high revision".

Originally, the intent was for "yes" and "no" to mean whatever the user
wanted it to mean, and figure out at runtime whether that made "yes" or
"no" the high rev. This feature was lost at some point (if it ever
existed) and "yes" was assumed to mean "high rev". This was confusing,
because the docs implied you could make "yes" or "no" mean whatever you

Now, we figure out from the bisect log which identifier is high, and
stick with that moving forward. Also, there's now a test testing the
"no is high" case.

13 of 3 results
You can't create new branches for Bazaar Bisect Plugin.