👍 Please update the changelog and we can get this merged! 😉

Wow, you cannot just delete migrations and let us deal with it when upgrading our sylius!
Please keep these migrations and add a new one from scratch to the first already existing migration.

@winzou all migrations will be available in v0.15, so you can use whatever you need. Then in order to jump to v0.16 you would need to run just one migration. We plan to make one migration file per release to ease upgrades (all PRs will introduce their migrations and just before release we will merged them all into one file).

Does it sound good for you or you have some better idea? (related discussion #3303)

@michalmarcinkowski done! :)

What is the point of merging migrations?

For this PR, I would checkout Sylius just before the first migration, then do a do:mi:di, then add the generated file here. It would keep history and ease migrations (what if I want to update from 0.14 to dev-master?). I just hope that every schema change has its migration...

@winzou New migrations will allow to migrate 0.15 -> 0.16 in just one migration. Development branch master will contain unmerged migrations so migrating 0.15 -> master would be easy to. The only drawback I can see is that migrating master -> next stable version would not be easily available - @michalmarcinkowski?