pDrupal 7 is moving along nicely, and is becoming increasingly stable. We just released a href=http://drupal.org/drupal-7.0-alpha2 rel=nofollowa second alpha release/a, fixing a number of critical bugs, following our initial alpha release in January. Alpha releases are to give Drupalistas something to download and test, so they can report and help fix bugs./p pWhen will we switch to betas? We will switch to betas when a href=http://drupal.org/project/issues/search/drupal?status[]=Openamp;issue_tags=D7+upgrade+path rel=nofollowthe upgrade path from Drupal 6 to Drupal 7 is working/a. Once we hit beta, we will become increasingly strict about accepting any more changes and we'll also commit to making HEAD to HEAD upgrades work./p pFinally, we'll start rolling release candidates once the a href=http://drupal.org/project/issues/search/drupal?version[0]=156281amp;status[0]=1amp;status[1]=8amp;status[2]=13amp;status[3]=14amp;priorities[0]=1amp;categories[0]=bugamp;categories[1]=task rel=nofollownumber of critical bugs/a is zero (or close to zero). To help us focus on critical bugs, we're working on a href=http://drupal.org/node/175555 rel=nofollowadding a 'major' severity level/a to our ticketing system, making the options 'critical', 'major', 'normal' and 'minor'. 'Major' bugs would be really bad, but not necessarily block a release. For example, bugs that don't prevent Drupal from working, or that only affect a fraction of the Drupal population would be prioritized for fixing in follow-up releases. Critical bugs are those that badly break Drupal, or that are a major regression compared to Drupal 6./p pa href=http://drupal.org/node/725382 target=_blankread more/a/p

Read more: http://drupal.org/node/725382