[Discussion] Remove Phalcon Migrations

[CameronHall]

I propose that we remove the Phalcon Migrations feature in the 4.0 revision of the Phalcon Developer Tools, in favor of CakePHP's Phinx.

It seems there are regular issues with the Migrations component, with 21.3% of the issues for this project related to the migrations tool alone. It makes sense, for us to offload this maintenance debt to Phinx as it is already production ready, battle tested and incredibly popular with 7M+ Downloads.

If necessary, we could compromise and create a wrapper for Phinx to maintain the functionality but offload the nitty gritty.

[Jeckerson]

Agree!

[ruudboon]

Agree. I would love to see the wrapper to handle the config parsing etc.

[Ultimater]

Wrapper sounds like fun.

[sergeyklay]

I'm ok with this. I think this may be implemented in the v4.0.x . But note we'll need to update the docs to refer to previous dev-tools version when mentioning previous implementation of migrations. We must also provide at least minimal documentation for the new implementation. And finally, what do you think guys about a migration converter or a solution (at least a tip) to use old migrations with the new version.

[Jeckerson]

@sergeyklay All what you mentioned is possible.

[CameronHall]

@sergeyklay this suggestion is only for v4.0.x. I suggest it now, as there is already a mass of backward incompatibilities between Phalcon 3 and 4, it's an appropriate time (at least I believe it to be) to also introduce backward incompatibilities to the developer tools as well.

I still think we should fix any "bugs" for the current revision. But no further work on NFRs.

[Jeckerson]

Another option is doctrine migrations - https://github.com/doctrine/migrations

[ruudboon]

Related #1315

[Jeckerson]

Closing in favor - #1339