[RFC] tortoise implementation design

[Mark Hammond]

Hi all,
  I've been following up the strategy document with some thoughts about the
implementation of tbzr, particularly the RPC mechanism used between the C++
client and the Python server.  In many ways it extends the "strategy"
document, but I think it makes the most sense to keep this as a separate
document - please let me know if you think otherwise.
 
All feedback appreciated!

In the meantime, I've been chatting with Alex Haro (who did the current tbzr
implementation) and he created a new team
(https://launchpad.net/~tortoisebzr-developers) and our current thinking is
to create a team branch and work from that.  I'm a little concerned though
that using a team branch implies we can't (or are discouraged from) making
local branches, and instead should perform a checkout.  My lack of bzr
experience is letting me down again, so I thought I'd ask for some advice
here: are there recommendations for how to best manage the code for this
work?  Maybe I should create a personal branch to work from, and the team
branch is merged to only when stable?

Thanks,

Mark
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tortoise-rpc-design.txt
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20080520/b9910d49/attachment-0001.txt