After a month-long Community QA, we are getting ready to deploy Drupal.org D7 upgrade. During the last couple of weeks we were limiting the number of ‘to-do before launch’ issues to those that are absolutely essential. Currently our launch blocker list consists of the 12 open issues.
We took a look at the upcoming Drupal events to find a quiet week, which won’t interfere with major camps and sprints, and..
Launch date
If by Monday, 28 of October, launch blocker issue is down to 0, we plan to deploy the Drupal.org D7 upgrade on Thursday, 31 of October.
If by Monday, 28 of October, the launch blocker issue count is higher than 0, we will have to postpone deployment for a few weeks.
What will the launch look like?
Drupal.org will be down for approximately 24 hours during deployment. It will be replaced by a static page with a download link for the latest Drupal release available. Sub-sites will stay online, but with user logins disabled. We realize this will be a significant inconvenience for users who rely on Drupal.org, and will try to bring it up as soon as possible.
We will start deployment around 15:00 UTC on October 31st. We expect the site to be back up by 15:00 UTC on November 1st.
Update: both updates.drupal.org and ftp.drupal.org will stay online. drush make / dl will work fine, update status module as well.
What if there are problems? Do you have a back up plan?
Yes, we do. If we encounter significant problems during migration, we will roll back to the Drupal 6 version of Drupal.org and restore backup made right before migration started.
How can I find out what’s going on during deployment?
Twitter accounts to follow are @drupal_org and @drupal_infra. IRC channels: #drupal and #drupal-contribute.
What changes will I see when the site comes back online?
Most pages on the site won’t change. Our goal for this project was straight port from Drupal 6 to Drupal 7. The only place where you will see significant UI changes is the issue page. Some time ago we wrote up this blog post, which explains what is changing and why in detail. We will also publish an F.A.Q. right before launch, which will list all changes you might encounter on the website.
How can I help?
To ensure we are able to launch on time, you can help us by bringing launch blockers count to 0.
Here are the issues:
Drupal Core
https://drupal.org/node/1289336
https://drupal.org/node/2001308
Search API
https://drupal.org/node/2110315
https://drupal.org/node/1832356
Project*
https://drupal.org/node/2044475
https://drupal.org/node/2097927
https://drupal.org/node/1991726
Comments
So maybe a dumb question, but
So maybe a dumb question, but will this outage block any drush make builds that reference modules on d.o during the downtime?
Wait for answer for this as
Wait for answer for this as well.
With sub-sites staying online
I will presume everything will be in read-only mode, so any module located on ftp.drupal etc shouldn't be affected.
That is correct.
That is correct.
No, it won't. drush make / dl
No, it won't. drush make / dl will work fine since they only interact with ftp.drupal.org and updates.drupal.org, both of which will stay up.
Why not straight to drupal 8?
So since drupal 8 supports direct migration from drupal 6, why not skip a complete version? A stable release won't be a very long time away...
Drupal 7 upgrade was the best
Drupal 7 upgrade was the best decision at the time when we started it, Drupal 8 was not ready at all.
Will http://api.drupal.org be
Will http://api.drupal.org be affected by this?
All sub-sites, such as: api
All sub-sites, such as: api.drupal.org, groups.drupal.org, localize.drupal.org will stay online, however user logins will be disabled. No one will be able to login.