View Single Post
Old 05-06-2011, 01:53 PM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,495
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I keep 2 sources locally. One is a copy of trunk called 'base', obtained with bzr pull. The other is my development branch (in fact I have 3). I use the bzr gui, which does these basic things very well and very easily.

All my branches use a shared repository. This makes pulls, pushes, and merging much faster.

Workflow:
  1. pull changes from launchpad to 'base'
  2. merge base into 'dev'
  3. make changes, do work, etc
  4. commit changes in dev. Often more than one commit.
  5. check if new changes are in base. If so, repeat steps 1 and 2 to ensure that there are no change conflicts.
  6. push changes from dev to my repository on launchpad. Kovid reviews and merges from there.
I have both base and dev so I can run from either to help debug, have rapid access to the change logs and diffs, and rarely to add print statements in the trunk code to help see what is going on. In the latter case, I revert the branch before pulling from launchpad.
chaley is offline   Reply With Quote