On Wed, 22 Sep 2010 09:05:42 -0500 Bruno Wolff III <br...@wolff.to> wrote:
> On Wed, Sep 22, 2010 at 12:35:01 +0200, > Tomas Mraz <tm...@redhat.com> wrote: > > > > - Avoid changing the user experence if at all possible. - this is > > too strong condition. In some cases fixing a bug might inevitable > > change the user experience and in some cases for example the user > > experience might be just severally improved with the new release. > > So IMO this should be reworded with much less strong wording such > > as 'Avoid major changes and worsening the user experience if at all > > possible.' > > Perhaps the definition of "user experience" needs to get fleshed out > a bit. I think the intent is that people should be able to easily do > whatever they were doing before the update the exact same way after > the update. If they need to learn something new after after the > update, that's a problem. Yeah, that would be something to clarify. The Board's vision statement has just: "Stable releases should provide a consistent user experience throughout the lifecycle, and only fix bugs and security issues." I guess I would agree that we want to avoid changes that require users to change their workflow or use of packages in a stable release (if we can avoid it). So, that would be, BAD: - Changing User interface (moving menu items or buttons around) - Changing names of commands for command line. - Changing behavior of command line options (ie, --foo does something totally different). - Server packages that require admin intervention to keep working (database schema changes, config files change options that need to be modified to the new way), etc. Of course there may be cases where we have to do these things, but they should be exceptions, not something people expect. kevin
signature.asc
Description: PGP signature
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
