Need help with workflow

[Alexander Belchenko]

Gordon Tyler пишет:
> So I persuaded my wife to use Bazaar (she's used svn in the past) for a
> small project that she's working on and everything is going fine so far.
> The setup is currently as follows:
> 
> On a shared server on our home network, there is a tree-less repo
> containing a trunk branch accessed via
> bzr+ssh://server/repos/project/trunk. On her PC, she has branched trunk
> into a directory, in which she makes changes, commits and then pushes up
> to the server when she wants to share the changes with me.
> 
> Now that she wants to create another branch for making some changes in
> parallel without disturbing the stability of the trunk -- a feature
> branch. However, this is complicated by the requirement that her working
> directory has to be in a specific location. We can't just create a repo
> and have subdirectories for the branches.
> 
> Would Neil's bzr-colo plugin be a good fit for this situation? What else
> would you suggest?

I want to say that colo is coolo! Zillions kudos to Neil!

bzr-colo is near to be perfect if you want to have multiple branches in the same directory. Now I'm 
better understand git users. I wish to have this plugin couple of year ago.

I'm changing all my plugins (qbzr, scmproj, explorer) to use bzr-colo for development. Before I've 
used light checkout pointing to branches in shared repo. So I have for example

C:\work\Bazaar\plugins\qbzr  # light checkout

and

C:\work\Bazaar\repos\qbzr-repo\       # shared repo
C:\work\Bazaar\repos\qbzr-repo\trunk  # its branch

Needless to say how it's bad for jumping back and forth between checkout and shred repo when I need 
to create new release of qbzr?


BTW, colo (if pronounced as kolo) in Ukrainian is a "circle". :-)