How about, no release until "0 critical bugs, drupal.org is upgraded, and 5 of the top 10 modules on http://drupal.org/project/usage are upgraded"? Of course, what you really want is for that metric to be met earlier in the cycle, so that some of the experience gained by upgrading drupal.org and the module can actually inform core. cheers, -tao Greg Knaddison wrote:
On Wed, Mar 4, 2009 at 11:29 AM, Aaron Winborn <winborn@advomatic.com> wrote: <great stuff>
My sense (hope?) is that Drupal7 will only be released when "0 critical bugs AND drupal.org is upgraded." I think this should solve most of the problem you cite because drupal.org now and increasingly relies on many of the major modules.
It may lead to some uncomfortable feelings (if we are 4 months after code freeze and no d.o upgrade in site, for example) but those uncomfortable feelings will fuel desire to work on the modules needed for d.o. That will also give time for developers of other modules.
Regards, Greg