On Thu, 11 Mar 2010, Paul W. Frields wrote: > As noted in our previous minutes[1], the Board was tasked with > producing a vision statement for updates to Fedora stable releases. > That vision can be found here: > > https://fedoraproject.org/wiki/Stable_release_updates_vision > > This statement is the result of many Board discussions which have > taken into consideration issues raised recently in numerous other > venues such as the devel list. After considering these issues > carefully, along with other factors such as the broad user base for > which we should strive[2], the Board feels this vision will best meet > the needs of our millions of users, including our contributor base. > > The Board would like FESCo to read through this vision statement, and > use it as a basis for implementing changes that will help achieve this > vision. We look forward to working with FESCo and across the whole > Fedora Project to continue improving the Fedora distribution. I believe that we should build the infrastructure to support these policy changes first. As Spot eloquently pointed out, the number of users who are likely to help promote packages from testing to stable is currently a vanishingly small number. We must first solve this problem. When we are satisfied that we've got tools that significantly increase participation in updates-testing, then *and only then* should we change the policies around updates-testing. Which, to me, means "build improved updates-testing flow for F14, change policy starting with F15". My $0.02. --g -- Educational materials should be high-quality, collaborative, and free. Visit http://opensource.com/education and join the conversation. _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
