Skip to content
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

Closed
3 of 7 tasks
etobella opened this issue Jul 8, 2020 · 12 comments · Fixed by #7
Closed
3 of 7 tasks

Backport to 12.0/11.0 #4

etobella opened this issue Jul 8, 2020 · 12 comments · Fixed by #7

Comments

@etobella
Copy link
Member

etobella commented Jul 8, 2020

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:

@pedrobaeza
Copy link
Member

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.

@etobella
Copy link
Member Author

etobella commented Jul 8, 2020

Sure! #5 created

@bennetblock
Copy link

bennetblock commented Jul 9, 2020

@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" ?

@pedrobaeza
Copy link
Member

Check the steps put in the main comment for the backport to 12.0, that are also applicable to 11.0

@pedrobaeza pedrobaeza changed the title Backport to 12.0 Backport to 12.0/11.0 Jul 9, 2020
@bennetblock
Copy link

@keshrath @muk-it - any doubts regarding backport to 11.0?

@etobella
Copy link
Member Author

@muk-it @keshrath Any news on this? It would be interesting to start working on the migration and we would like to know if there is any issues now that we have defined migration scripts for your original modules

@keshrath
Copy link
Member

@muk-it @keshrath Any news on this? It would be interesting to start working on the migration and we would like to know if there is any issues now that we have defined migration scripts for your original modules

Lets do it :)

@etobella
Copy link
Member Author

@pedrobaeza May be possible to create the branches in order to start the creation? I don't know if it is needed something 😄

@pedrobaeza
Copy link
Member

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.

@etobella etobella linked a pull request Jul 27, 2020 that will close this issue
@etobella
Copy link
Member Author

@bennetblock Will you try to backport to 11.0?

@bennetblock
Copy link

@etobella - yes, we are working on it

@pedrobaeza
Copy link
Member

Closed as done for 12.0, and if 11.0 comes ever, no need to track this as issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants