[RFC] rename migration folder

[legalsylvain]

When making a patch on a migration script, we have to rename the migration folder with the same name as the bumped revision. It could be automated.

I think that it could be an option of the ocabot. like bump-migration. the patch / minor / nobump / major is a choice of the people that are merging. (maintainers) not a choice of the developper.

CC : @sbidoul : what do you think ?

Ref : https://github.com/OCA/server-ux/pull/213/

[sbidoul]

Sounds interesting.

[hparfr]

Hi,

I think we can achieve it if in the merge requests we:

• 1) tell the developper puts the migrations scripts in the directory 0.0.0/
• 2) adapt oca-ci, to always increment version number of the module before running the tests
• 3) adapt oca-bot bump to rename the directory 0.0.0 to the new version number

1) should be possible according to odoo

        A special folder named ``0.0.0`` can contain scripts that will be run on any version change.

2) with a temporary / throw-away version number like major.minor.patch+1

[hparfr]

FYI @sebastienbeau

[legalsylvain]

tell the developper puts the migrations scripts in the directory 0.0.0/

That can not be asked to developpers. Sometimes, it is not possible to write idempotens scripts.

[hparfr]

I don't think migrations scripts have to be idempotants.

It should allow to run migration scripts and do not generate conflicts on github/oca pull requests.

With my proposal we may break the workflow when someone checkout pr - branches instead of stable.

One should adapt his tooling to manage modules containing a migrations/0.0.0 by doing the kind of steps (increment manifest and name the migration directory with the good version) to apply after the checkout instead of in the PR.

[legalsylvain]

I didn't understood your proposal i think. On the meantime, i'm not sure to be agree with what i wrote 3 years ago. Let's talk about that topic in the next oca days.