On 08/06/2009 05:46 PM, John Poelstra wrote: > Features are expected to be "complete enough" (testable) by Feature Freeze. Would it make sense to have the feature owner define what "complete enough" is going to mean when the feature is targeted for a release? Something the Feature Wrangler could approve, perhaps? Sure, there might be some unexpected things requiring revision, but most of the work would be front-loaded, and exceptions can be dealt with as that. With an up-front expectation, at least everybody would be singing off the same page as to what 100% means per feature. There's such variation with upstream release dates before and after Alpha that it's hard to see a single set of guidelines that will cover all cases. -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 http://www.bfccomputing.com/ Cell: 603.252.2606 Twitter, etc.: bill_mcgonigle Page: 603.442.1833 Email, IM, VOIP: bill@xxxxxxxxxxxxxxxx Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
