[MERGE/RFC] Userdoc Driven Design on the Bazaar 2.0 UI

[Robert Collins]

On Thu, 2009-04-16 at 17:01 +0900, Stephen J. Turnbull wrote:
> 
> What I'm hearing from Robert Collins is that there are fundamental
> design decisions driving many of these issues, and it will be a
> boatload of work to change them.  Maybe there's room for me to buff up
> my Python and get hired by Canonical. ;-)

It might be very easy to fix them; what I'm saying is that we should be
examining the internals with a view to creating a goal to aim for; then
we can look at whether we have time, what is needed, things we could do
now/temporarily on the way and so on.

Things that come to mind that are central to the way we share history
are: garbage-collection, finding names for (branch|merge|switch|push|
pull), reusing-history-when-running-'branch',
managing-a-collection-of-branches, 'mv a branch can break its history'.

All of these items are current serious usability issues that I see new
users struggling with routinely. I don't have an answer yet - I've been
thinking about repository guts, and networking almost exclusively for
some time now - but I'm sure we can come up with one that addresses them
all - or most. They seem connected to me.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090416/0c4e94b1/attachment.pgp