Drupal.org updated to Drupal 7
Running update Drupal.org confirmed. On October 28th, 0 critical update errors and performance tests look good, so the launch date is scheduled for Thursday, October 31st, 2013.
Drupal.org will be turned off for about 24 hours during deployment. The site will be replaced with a static page with a link to download the latest release of Drupal. Sites running on subdomains will be available, but without user authorization. Both updates.drupal.org and ftp.drupal.org will be online. Drush make / dl will work fine, just like the update status module.
The launch of the new version is planned for October 31 at 19:00 Moscow time. It is expected that the site will be available on November 1st at 19:00.
')
If you have problems updating
In case of problems during the upgrade, Drupal.org will be rolled back to Drupal 6 and recovered from the backup made before the migration.
Where can I follow the update process?
On twitter @drupal_org and @drupal_infra , as well as on the #drupal and #drupal IRC channels.
What changes will be noticeable when the site becomes online?
Information on changes in the functionality or user interface can be found on the Drupal.org D7 FAQ page. Most pages will not change their appearance or their functions. Our goal in this project is to migrate from Drupal 6 to Drupal 7. The only place where there will be significant changes in the user interface is the issue page (issue page). In this post you can learn more about what will be changed on the question page and why. In general, Drupal 7 gives us more opportunities to introduce new features, and there will also be a performance boost for some pages.
Why not wait and upgrade to Drupal 8 when it comes out?
The upgrade to Drupal 7 began in March 2012. The upgrade took longer than we expected because of a number of reasons, such as the size and complexity of Drupal.org, as well as resource constraints. We decided to move forward and complete the upgrade on Drupal 7 so that Drupal.org works on the latest Drupal release, and so we can use the lessons in future updates.
Drupal.org will be turned off for about 24 hours during deployment. The site will be replaced with a static page with a link to download the latest release of Drupal. Sites running on subdomains will be available, but without user authorization. Both updates.drupal.org and ftp.drupal.org will be online. Drush make / dl will work fine, just like the update status module.
The launch of the new version is planned for October 31 at 19:00 Moscow time. It is expected that the site will be available on November 1st at 19:00.
')
If you have problems updating
In case of problems during the upgrade, Drupal.org will be rolled back to Drupal 6 and recovered from the backup made before the migration.
Where can I follow the update process?
On twitter @drupal_org and @drupal_infra , as well as on the #drupal and #drupal IRC channels.
What changes will be noticeable when the site becomes online?
Information on changes in the functionality or user interface can be found on the Drupal.org D7 FAQ page. Most pages will not change their appearance or their functions. Our goal in this project is to migrate from Drupal 6 to Drupal 7. The only place where there will be significant changes in the user interface is the issue page (issue page). In this post you can learn more about what will be changed on the question page and why. In general, Drupal 7 gives us more opportunities to introduce new features, and there will also be a performance boost for some pages.
Why not wait and upgrade to Drupal 8 when it comes out?
The upgrade to Drupal 7 began in March 2012. The upgrade took longer than we expected because of a number of reasons, such as the size and complexity of Drupal.org, as well as resource constraints. We decided to move forward and complete the upgrade on Drupal 7 so that Drupal.org works on the latest Drupal release, and so we can use the lessons in future updates.
Source: https://habr.com/ru/post/199510/
All Articles