In https://doc.ez.no/display/DEVELOPER/Updating+eZ+Platform we describe an upgrade process that is lengthy and awkward. There are zero (0) occurrences of the word "rebase" in the entire process, and we ask users to manually resolve merge conflicts.

As a developer, I want a simple, automated process for updating/upgrading my installation of eZ Platform, so that I can quickly test the results and implement with minimal issues. As a pragmatist, I would settle for documentation that walks me through a simpler upgrade process.

Suggestion: add ezsystems/ezplatform as a git remote, create a branch from your current project, rebase from ezsystems/ezplatform's desired tag or master branch, and push the result to your own repo.

Primarily a documentation task at first, with discussion about CLI automation from Engineering.