v2.x Revamp Requirements

[DavidLiedle]

(Using notes from @andrerom to try to create an overall epic for v2 requirements)

v2 Revamp Requirements Epic

Scope

This Epic defines requirements and approaches for further activities moving towards eZ Platform 2.x, focused on DX in four areas:

1. Quality Control (BDD, Specification, Documentation)
2. Performance by Design (REST API optimizations)
3. Modern Architecture (Symfony 3.x, Future-Proof UI)
4. Development Process Awesomeness (Extending, Pipeline, Tooling, SDKs)

Stories under this Epic will fall under one of the above four categories (QC, PbD, MA, DPA), and may spin off into Epics of their own as we iterate.

This Epic will be "done" when there is a Markdown document in the specs repo defining overall project requirements and linking to their associated issues.

Requirements for v2 Solution:

Non-functional

• 2018-class browsers, implying support for
  • ES2016 or better
  • HTML5.1 or better
  • ...
• PHP 7.0 (as of Debian 9 available in all linux distros we support)

Functional

Compared to 1.7.0 LTS, 2.x should be:

• Minimum 2x faster in Production and 3x in Development
• Minimum 3x faster to extend, in common use cases like:
  • UI Menu Items with Symfony own modules views
  • Field Types
  • ...
• Have higher quality (less known defects). Common scenarios should "just work.":
  • Multi Site
  • Multi Language
  • ...
• Each feature should contain raw documentation from Dev and Spec from PM, so external testers and documentation team have enough content to make user documentation and blogs.

---

This issue may be used for discussion below.

[DavidLiedle]

Discussed in Epic Planning this morning:

• [ ] Capture User Stories (Use Cases) in Markdown at ezsystems/specs