<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 28/04/2016 07:33, Jim Porter wrote:<br>
</div>
<blockquote
cite="mid:d56a7633-10d9-6151-1ba0-19c39a9886de@gmail.com"
type="cite">
<pre wrap="">Therefore, I'd like to propose the following: any change to
Thunderbird's defaults should have a super-review before landing.
Super-reviewers would be especially focused on making sure that changes
meet most or all the following conditions, in descending order of
importance:
1) No data/program state should be lost.
2) Before changing a default, we should be sure the new default is
fully-operational.
3) Users should have an easy path to roll back to the previous UI/UX if
they don't like the new version. If possible, ask the user *before*
upgrading them.
4) It should be easy for users to find out what's changed, along with
instructions for how to adjust the new behavior to their liking.
</pre>
</blockquote>
I wished we had done that for 3.0. We changed so many UI default
that some people stayed on 2.x forever :( It was so bad that one of
the new default was reverted in 3.1. (grouped inbox versus account
inbox for those wondering).<br>
<br>
I do believe that ui changes are easily accepted if noyt noticeable
at first :)<br>
<br>
so I'd +1 jim proposition.<br>
<br>
Ludo<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
:Usul in #moc on irc.mozilla.org
Mozilla Operation Center
<3 ipv6 , <3 Gaming , <3 OSS
<a class="moz-txt-link-freetext" href="http://sietch-tabr.tumblr.com">http://sietch-tabr.tumblr.com</a></pre>
</body>
</html>