Implement sharding already in the migrations

.appveyor.yml

@@ -13,7 +13,9 @@ cache:
 
 environment:
   matrix:
-    - php: 7.2
+    - php: 7.2.23
+    - php: 7.3.10
+    - php: 7.1.32
 
 init:
   - SET PATH=C:\Program Files\OpenSSL;c:\tools\php;C:\tools\composer;%PATH%
@@ -25,14 +27,15 @@ install:
     - ps: |
         # Check if installation is cached
         if (!(Test-Path c:\tools\php)) {
-          appveyor-retry cinst --params '""/InstallDir:C:\tools\php""' --ignore-checksums -y php --version ((choco search php --exact --all-versions -r | select-string -pattern $env:php | sort { [version]($_ -split '\|' | select -last 1) } -Descending | Select-Object -first 1) -replace '[php|]','')
+          appveyor-retry cinst --params '""/InstallDir:C:\tools\php""' --no-progress --ignore-checksums -y php --version $env:php
           # install sqlite
-          appveyor-retry cinst -y sqlite
+          appveyor-retry cinst -y sqlite  --no-progress
           Get-ChildItem -Path c:\tools\php
           cd c:\tools\php
 
           # Set PHP environment items that are always needed
           copy php.ini-production php.ini
+
           Add-Content php.ini "`n date.timezone=UTC"
           Add-Content php.ini "`n extension_dir=ext"
           Add-Content php.ini "`n memory_limit=1G"

.travis.yml

@@ -36,6 +36,7 @@ jobs:
 
     - stage: Test
       env: COVERAGE
+      php: 7.2
       before_script:
         - mv ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/xdebug.ini{.disabled,}
         - if [[ ! $(php -m | grep -si xdebug) ]]; then echo "xdebug required for coverage"; exit 1; fi
@@ -47,10 +48,12 @@ jobs:
 
     - stage: Code Quality
       env: CODING_STANDARDS
+      php: 7.2
       install: travis_retry composer install --prefer-dist
       script: ./vendor/bin/phpcs
 
     - stage: Code Quality
       env: STATIC_ANALYSIS
+      php: 7.2
       install: travis_retry composer install --prefer-dist
       script: vendor/bin/phpstan analyse

UPGRADE.md

@@ -1,3 +1,73 @@
+# Upgrade to 3.0
+
+- The "version" is the FQCN of the migration class (existing entries in the migrations table will be automatically updated).
+- `MigrationsEventArgs` and `MigrationsVersionEventArgs` expose different API, 
+please refer to the [Code BC breaks](#code-bc-breaks) section.
+
+## Console
+- Console output changed. The commands use a different output style. If you were relying on specific output, 
+  please update your scripts. 
+  Console output is not covered by the BC promise, so please try not to rely on specific a output.
+  Different levels of verbosity are available now (`-v`, `-vv` and `-vvv` ).
+
+## Migrations table
+
+- The migrations table now has a new column named `execution_time`.
+
+
+## Configuration files
+
+*migrations.php Before*
+```php
+<?php
+
+return [
+    'name' => 'My Project Migrations',
+    'migrations_namespace' => 'MyProject\Migrations',
+    'table_name' => 'doctrine_migration_versions',
+    'column_name' => 'version',
+    'column_length' => 14,
+    'executed_at_column_name' => 'executed_at',
+    'migrations_directory' => '/data/doctrine/migrations-docs-example/lib/MyProject/Migrations',
+    'all_or_nothing' => true,
+    'check_database_platform' => true,
+];
+```
+*migrations.php After*
+
+```php
+<?php
+
+return [
+    'name' => 'My Project Migrations',
+
+    'table_storage' => [
+        'table_name' => 'doctrine_migration_versions',
+        'version_column_name' => 'version',
+        'version_column_length' => 1024,
+        'executed_at_column_name' => 'executed_at',
+        'execution_time_column_name' => 'execution_time',
+    ],
+
+    'migrations_paths' => [
+        'MyProject\Migrations' => '/data/doctrine/migrations/lib/MyProject/Migrations',
+        'MyProject\Component\Migrations' => './Component/MyProject/Migrations',
+    ],
+
+    'all_or_nothing' => true,
+    'check_database_platform' => true,
+];
+```
+
+Files in XML, YAML or JSON also changed in a similar way. Please refer to the official documentation for more details.
+
+## Code BC breaks
+
+Most of the code is protected by the `@internal` declaration and in a very rare cases you might have dealt with the 
+internals of this library. 
+You can use [Roave/BackwardCompatibilityCheck](https://github.com/Roave/BackwardCompatibilityCheck) and get a list of 
+changed elements.
+
 # Upgrade to 2.0
 
 ## BC Break: Moved `Doctrine\DBAL\Migrations` to `Doctrine\Migrations`

composer.json

@@ -23,11 +23,12 @@
         "doctrine/coding-standard": "^6.0",
         "doctrine/orm": "^2.6",
         "jdorn/sql-formatter": "^1.1",
-        "mikey179/vfsstream": "^1.6",
-        "phpstan/phpstan": "^0.10",
-        "phpstan/phpstan-deprecation-rules": "^0.10",
-        "phpstan/phpstan-phpunit": "^0.10",
-        "phpstan/phpstan-strict-rules": "^0.10",
+        "mikey179/vfsStream": "^1.6",
+        "phpstan/phpstan": "^0.11",
+        "phpstan/phpstan-deprecation-rules": "^0.11",
+        "phpstan/phpstan-phpunit": "^0.11",
+        "phpstan/phpstan-strict-rules": "^0.11",
+        "phpstan/phpstan-symfony": "^0.11.6",
         "phpunit/phpunit": "^7.0",
         "symfony/process": "^3.4||^4.0||^5.0",
         "symfony/yaml": "^3.4||^4.0||^5.0"
@@ -51,7 +52,7 @@
     },
     "extra": {
         "branch-alias": {
-            "dev-master": "2.2.x-dev"
+            "dev-master": "3.0.x-dev"
         }
     },
     "bin": [