Some questions I have are:
- When should I use bzr over a centralized VC like Subversion?
- How do you start to use bzr on a project?
- Can bzr be used along side another VC (e.g. SVN for main repo but keep your personal branches in bzr)?
- What is the standard workflow in bzr (e.g. svn => update, status, commit)?
- What tools can be used to share your code?
- What do you *love* about bzr?
- What do you *hate* about bzr?
--Edavis 11:52, 30 September 2007 (PDT)
* What tools can be used to share your code?
typically, sftp access to a web server. but ftp, sftp, http, or file URLs all work.
there is a plugin for trac to use bzr: http://packages.debian.org/trac-bzr
* What do you *love* about bzr?
- merging support is very good
- publishing a branch is as simple as pushing to a web-accesible space
- uncommit: habit of commit freely, but only push what's good
- offline editing
* What do you *hate* about bzr?
the software is under rapid development, and backwards compatibility is not always stellar (i.e. checking out a branch created with a newer version of bzr may not work). versions 0.16+ are considerably more stable as far as format changes.