We are planning 2.0-RC1 around DrupalCon New Orleans (or later).
By that time Drupal 8.1 will be released and 8.0 will no longer be supported.

8.1 brings BC-breaking changes to migrations.
It also contains pieces of the contrib Entity API which we can remove from the contrib now that they're committed.
List of contrib Entity API pieces committed to 8.1 so far:
- add-page route generation
- add-form route generation
- rendered entity views handler
- base entity property generation (replacement for EntityKeysFieldsTrait)
- RevisionableContentEntityBase (+ RevisionLogInterface)
- Param converter and route enhancer for revisions
We're using everything except the revision stuff, and we're planning to start using the revision stuff once products become revisionable.

To ensure we're ready for these changes, we should start requiring Drupal 8.1 for beta1 (along with an 8.1 compatible branch of Entity API).

Comments

bojanz created an issue. See original summary.

bojanz’s picture

Issue summary: View changes
bojanz’s picture

Issue summary: View changes

Btw, Drupal 8.1 RC1 is out on March 16th, before our beta.

agoradesign’s picture

March 16th was the original plan - it seems, this has changed. The release notes of beta1 say: "We expect to release a release candidate for 8.1.0 on April 6th, and 8.1.0 stable on April 20th." (https://www.drupal.org/drupal-8.1.0-beta1)

bojanz’s picture

@agoradesign
Thanks, that's good to know. Since our beta1 plan is "end of March", we should probably time it for April 6th then.

bojanz’s picture

Issue summary: View changes
bojanz’s picture

Title: Require Drupal 8.1 for 2.0-beta1 » Require Drupal 8.1

We should do this soon.

Opened a PR: https://github.com/drupalcommerce/commerce/pull/361

  • bojanz committed cf7a605 on 8.x-2.x
    Issue #2682067: Require Drupal 8.1
    
bojanz’s picture

Status: Active » Fixed

Merged.

bojanz’s picture

Updated the installation docs: http://docs.drupalcommerce.org/v2/install.html and added a note to the project page.

Londova’s picture

There is still an error during Commerce installation / Commerce Order.
I'll report this as a separate issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.