Demonstration Help.

[Talden]

> Any ideas/features I should focus on as well?

Well, if your developers are like ours (or me) you'll have many
branches live in the project at a time and the devs may have several
on their machine.  So...

1. Shared Repositories

I know you're focusing on centralised but if you cover local branches
consider the following

2. Keeping a clean mirror of upstream

If your devs want to separate the area of their drive for upstream
mirrors and local branches from the work areas then talk about
tree-less branches, no-trees in repositories and switching between
branches in lightweight checkouts.


On general working-tree management, point out the true-renames and the
ability to apply them after the actual change

EG
$ move a.txt b.txt
$ bzr mv --after a.txt b.txt

Devs using tools without bzr integration will require knowing how to
match up the moves before a commit.

PS: Does anyone know if qbzr/tortoiseBzr has support for or plans for
a nice drag'n'drop matching tool for missing files and unversioned
files.  That is, a GUI means of applying "bzr mv --after [src] [dest]"

--
Talden