[RFC] proposed user doc for nested trees

[Maritza Mendez]

On Sun, May 10, 2009 at 4:16 PM, Ian Clatworthy <
ian.clatworthy at internode.on.net> wrote:

> Thanks for the positive feedback. As well as being good for my ego, it's
> nice to hear that we're heading in the right direction. If users don't
> speak up, it can mean "I silently accept" but it can also mean "you've
> confused me so I won't say anything".
>

No problem.  Software is usually noticed for what goes wrong, not right.
And this is even more true for documentation.  It's important to speak up
about what is good.  FWIW, the focus on documentation is probably a big
factor in why svn achieved so much mindshare early.  Documentation matters a
lot.  And documentation will drive the adoption of bzr, possibly even beyond
what svn has achieved, because the people who have suffered with centralized
vcs seem to be the best at appreciating dvcs.


> I certainly hope though that you'll only need the manual open the first
> few times you use the feature. If not, I'd be concerned that the mental
> model was not good enough and still needed some work.


You may be right.  The people most likely to use nested branches are build
managers and project leaders.  They should know this stuff.  I might keep
the manual open just to to feel good.

-M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090510/c467ddfd/attachment.htm