On Mon, 09 Aug 2010 09:16:03 -0400 seth vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote: > On Mon, 2010-08-09 at 08:58 -0400, Tom "spot" Callaway wrote: > > On 07/23/2010 11:55 AM, Kevin Fenzi wrote: > > > I'd like to propose modifying the statement somehow. > > > Perhaps something like: > > > > > > Stable releases should strive to provide a consistent user > > > experience throughout the lifecycle, focusing on bug and security > > > fixes. > > > > I'm not a fan. I think this is roughly the policy that we have > > today, which has caused so much strife. Surely, there will be > > exceptions, but this wording makes the exception the rule. > > > > Or, to put it blunt, if you say "should" and "strive to", you need > > to realistically replace with "won't". > > > > +1. If you put in weasel words to begin with then people will use them > to weasel their way out of complying with the INTENT of the rule. ok. I can see that viewpoint. I guess where I'm confused is that I think there will be exceptions to this in some cases. Is the Board ok with us having an exception policy? Or should the statement be absolute? Sometimes bug fixes and security fixes will require that new features or user experience changes happen to. This is far from ideal, but when the choice is between: broken, insecure, or new; new is better than the alternatives in some cases. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
