127: Bazaar backend

elliot*******@gmai***** (Google Code) (Is this you? Claim this profile.)
April 22, 2008
Enhancement request for a bazaar backend.

I've started working on this, definitely willing to collaborate with anyone
else who is interested. It's been discussed on the mailing list a bit, but
I'm adding this issue to the tracker so that others can see it is being
worked on. I don't think I can assign the issue to myself to indicate that
I'm working on it.

Currently the main challenge I am facing is that Bazaar does not include
version numbers in the diffs, only timestamps, and that the diff file
parsing is not done by individual SCMTool classes, but all in a single
location.

My current thinking is that it would be good to slightly refactor diff
parsing to be done by the SCMTools, perhaps making the current parsing the
default implementation. I would then override the diff parsing for the
Bazaar SCMTool class, and require Bazaar bundles to be submitted, rather
than patches. The bundles would include revision numbers.
#1 elliot*******@gmai***** (Google Code) (Is this you? Claim this profile.)
Type-Enhancement
david
#2 david
Gotta love (hate) google code's non-developer issue tracker UI =P
  • -Type-Defect
    +Type-Enhancement
    +Component-SCMTools
#3 henrik.*******@oul**** (Google Code) (Is this you? Claim this profile.)
Any progress on this?

I wrote a simple add-on, and uploaded it here:

http://reviews.review-board.org/r/296/

I hope that would be a solution for the issue.
#4 jon.m*****@gmai***** (Google Code) (Is this you? Claim this profile.)
I'm taking the bazaar support for a spin -- even though I use git usually one of my
clients is using bazaar.
david
#5 david
We've got a basic bazaar SCMTool now.
  • +Fixed