Scoping the UI changes for 2.0

[Mark Shuttleworth]

I agree that we have missed the window for designing a clean UI for bzr
2.0, and that it is more important to deliver the things we DID design
and commit to, on time.

However, I think the Bazaar team needs to recognise that existing
evolutionary processes have resulted in a poor UI experience, despite
having lots of good people who feel like they care about this. Therefor,
I would like to see a commitment to a focus on this in the 3.0 cycle,
starting with a cogent sprint that includes this.

The experience includes the command UI, as well as the documentation, as
well as the plugin management story, as well as our policy and
philosophy of format management.

Somehow, we have come to a point that the Bazaar community thinks it's
OK for there to be more than 10 formats "out there in common use",
multiple development formats (6!!), rich-root and non-rich-root formats,
and all sorts of bad interactions with network servers of various versions.

During the 3.0 cycle, I would like to see:

 - a sprint and design focus on the command UI
 - a commitment to having ONE stable format throughout, and ONE
development format EVER in 3.0,
 - no rich-root / non-rich-root nonsense, ever again
 - a website and documentation which are a pleasure to learn and use
 - a framework for managing plugins that includes all the lessons from
Firefox - compatibility test, automatic updates

Bazaar is wonderful. But it seems most wonderful for the people who are
tightly engaged, who are happy to run branches with experimental
formats. The problem IS NOT SOLVED till it is solved in the default
format for all users, out of the box.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090417/6d61d235/attachment.htm