Backward compatibility for data, not code • Two latest releases supported • Site upgrades required every ~6 years • Allows for radical improvements • E.g. Node system would probably never have happened if backwards compatibility was maintained
Aim - provide a core solution (API) for problems that contrib address: • Display Suite, Context, Panels, Ctools Page Manager. • Responsive layout builder – didn’t make it in time (pushed to D9). • https://groups.drupal.org/node/287563
8 ships with all responsive themes (Bartik, Seven and Stark) • Breakpoint and Picture modules now in core. • Improved CSS and JS performance • Spark – D7 distribution. • Usability – CK Editor in core. In place editing.
Drupal spits out HTML • D8 is a web service • Rest server • Expose Views as a serialized resource • Guzzle – replace drupal_http_request • PHP Unit – dependency injection
changes are still allowed during the clean-up phase until the API freeze deadline, so long as they do not significantly increase the overall technical debt.”
“The primary purpose of this phase is to resolve release-blocking issues, and backwards compatibility- breaking API changes are only allowed when they are needed to fix major and critical bugs and tasks.”