>> The feature process can be very forgiving when there is *information* on >> the feature page about how "testable" a particular feature is or further >> information what is left to be done past feature freeze. >> >> I don't currently have the ability to know what every upstream project >> is doing or know what every developer plans to do "real soon now" ;-) >> Thus it helps to add it to the feature page :) >> >> As a result my goal is to treat every feature page equally, using the >> information that has been provided on each page, in light of the feature >> process that everyone has agreed on. As always, the feature process is >> not written in stone and if there are ways the current process should be >> amended or changed I'm sure FESCo would be open to constructive >> suggestions to changing it and making it better. > > From the sidelines it seems that there is a confusion on what the % > actually means. Some think that 100% means "ready to be tested" and > others think that 100% means "It's been tested, the final builds are in > and all known and cared about bugs are fixed". My understanding was the later. All working tested and ready to go. What is it meant to mean. Peter -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
