Download drupal-8.0.0-rc1.tar.gztar.gz 10.97 MB
MD5: 58841f02728a85c105ce988e5605e4e5
SHA-1: 485393cadec107020f5b76b559662e7490cc5690
SHA-256: 0afdf737fd884f32c17ae0fc5174f7989c5909746e6c9a701bd9bcb99a1caa58
Download drupal-8.0.0-rc1.zipzip 19.35 MB
MD5: 2668fa1b02adf10624cba9361c37ffcb
SHA-1: 4dd8885751be99214ce1e313d030632c70a60075
SHA-256: a14e39c8e3c938898397362c6d471ef181fb4245129da03cee63a1115687d523

Release info

Created by: catch
Created on: 7 Oct 2015 at 21:27 UTC
Last updated: 24 Feb 2016 at 19:56 UTC
Core compatibility: 8.x
Release type: Bug fixes

Release notes

This is the first release candidate for Drupal 8.0.0. Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release. Release candidates also provide an opportunity to begin developing with Drupal 8, especially for:

  • New sites.
  • Sites that rely mainly on the expanded functionality provided by Drupal 8 core alone.
  • Projects that will take months of development time.
  • Sites for which Drupal 8's benefits outweigh the effort needed to port (or work around) contributed modules that do not yet have Drupal 8 versions.

Read more about Drupal 8.0.0-rc1.

When will Drupal 8.0.0 be released?

We will schedule an official release date for 8.0.0 when we are confident that the rate and nature of incoming critical bugs has slowed enough to ensure a stable release. Until then, release candidates of Drupal 8 will be released twice a month alongside Drupal 7 release windows.

Known issues

There are currently 0 known critical issues with this release candidate. We expect to identify and resolve additional critical issues as the release candidate is tested more widely.

There is a known issue with response cache headers sometimes exceeding hosting configuration limits that may cause some pages to not be viewable on some hosting providers. If you run into this, see that issue and its related issues for details.

Handling security issues

Starting now, any security issues discovered for Drupal 8 should be kept confidential and reported using the Report a security vulnerability link on the Drupal project page in order to protect existing sites. Through December 31, 2015, the Drupal 8 security bounty is also still active, so you can get paid for finding security issues and reporting them in our private tracker! See the security team page for more information on Drupal security.

Changes since 8.0.0-beta16

A handful of backward compatibility breaks were introduced since beta 16 in preparation for the release candidate, which may require updates to existing modules and themes:

Also see the full list of API changes in Drupal 8.

All changes