9.0 [mig] marketing_security_group

[cubells]

Renaming module marketing_security_group to mass_mailing_security_group

cc @Tecnativa

[rafaelbn]

Hi @cubells ,

It doesn't work. For example, demo user cannot delete it's own mass mailings. Check image:

Please review

Thanks!

[pedrobaeza]

The branch is not correct. You have to check again your git-fu.

[cubells]

@rafaelbn
this commit OCA/OCB@6375a4b changes the rules.

Now user can delete his own mass_mailing campaigns if belongs to Lead Automation user group, not to marketing group.

And it works.

[yajo]

Renaming module marketing_security_group to mass_mailing_security_group

If you rename an addon, you need to write a migration script.

---

These 2 commits have the same message:

We need to have descriptive messages for commits, to know what you are doing in each of them and why. It only takes some seconds and you help all of us.

---

Your branch has conflicts:

Please do a rebase or merge and fix them.

Thanks 😉

[pedrobaeza]

There's no need for a migration script, but a rename in the apriori.py file in OpenUpgrade, but he knows that and will make the PR when this one is merged.

[pedrobaeza]

@cubells please check this.

[cubells]

done.

@Tecnativa

He's on holidays and his concerns have been attended

[pedrobaeza]

Module renamed in OpenUpgrade in OCA/OpenUpgrade@544f656