Scoping the UI changes for 2.0

[Robert Collins]

On Fri, 2009-04-17 at 11:43 +0100, Mark Shuttleworth wrote:

> 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.

I hope its just perception that we think this is ok - I certainly don't.
We currently have only one development format - but there have been 6
revs to the beta formats since we started doing them - but at any one
time there is only one beta format. For the network side, the current
interactions are primarily data driven, and Andew and I are completely
focused on fixing them asap.

> 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.

I completely agree with this.

-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/20090429/927da644/attachment-0001.pgp