bzr for packaging

[Matt Zimmerman]

On Fri, Mar 09, 2007 at 08:55:43AM +0100, Martin Pitt wrote:
> == common practice that I found to work well ==
> 
> * Keeping bzr and Debian changelog in sync. I usually write the Debian
>   one and use [1] to automatically generate a bzr one. However, this
>   could become a more official and better integrated tool (plugin
>   instead of a shell wrapper).
>   
> * Keeping the changelog release as 'UNRELEASED' while committing
>   changes. This makes it easy to see for other people that they must
>   not start a new package revision. As a very last step before
>   uploading, s/UNRELEASED/feisty/ and 
> 
>     bzr commit -m 'release as 1.2-3 to feisty'
> 
>   so that it is easy to retrieve older package versions just by
>   looking at bzr log.

Do you keep the entire package in bzr, or only the debian directory?  If the
former, how do you go about merging new upstream releases?

Do you use a tool like debcommit for committing your changes?

-- 
 - mdz