-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport to 12.0/11.0 #4
Comments
About the migration scripts from MuK, please do the PR now that the module is merged, adding conditions for checking if coming from MuK or from this possible backport. |
Sure! #5 created |
@pedrobaeza - should we discuss backport to 11.0 here? We are ready to start and just need to align with you. Maybe we should rename issue to generic backport then? Could you add task "Create brnach 11.0" ? |
Check the steps put in the main comment for the backport to 12.0, that are also applicable to 11.0 |
@pedrobaeza May be possible to create the branches in order to start the creation? I don't know if it is needed something 😄 |
Branch created. As we are starting from scratch, I have kept pre-commit and all the new 13.0 stuff also for 12.0, and this will also make easier the backport. |
@bennetblock Will you try to backport to 11.0? |
@etobella - yes, we are working on it |
Closed as done for 12.0, and if 11.0 comes ever, no need to track this as issue. |
As we talked on #1 It is interesting to backport the dms module to 12.0 following the OCA guidelines.
There are several steps to follow:
The text was updated successfully, but these errors were encountered: