[16.0][MIG] partner_affiliate: Migration to 16.0 #1432
Conversation
* [MIG] Migration of partner_affiliate to v11 * Fixing use of @Class and do not inheriting address from parent company * Improving legibility and details of fields * Fixing travis errors remove obsolete .pot files [ci skip] [UPD] Update partner_affiliate.pot
[IMP] partner_affiliate: Readme [IMP] Small readability improvements [FIX] Remove copyright from init files [UPD] README.rst [UPD] Update partner_affiliate.pot Update translation files Updated by Update PO files to match POT (msgmerge) hook in Weblate. [UPD] Update partner_affiliate.pot Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: partner-contact-12.0/partner-contact-12.0-partner_affiliate Translate-URL: https://translation.odoo-community.org/projects/partner-contact-12-0/partner-contact-12-0-partner_affiliate/
[UPD] README.rst Translated using Weblate (Spanish) Currently translated at 100.0% (9 of 9 strings) Translation: partner-contact-12.0/partner-contact-12.0-partner_affiliate Translate-URL: https://translation.odoo-community.org/projects/partner-contact-12-0/partner-contact-12-0-partner_affiliate/es/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: partner-contact-13.0/partner-contact-13.0-partner_affiliate Translate-URL: https://translation.odoo-community.org/projects/partner-contact-13-0/partner-contact-13-0-partner_affiliate/
I tried to improve the description to be more precise about what this module does.
Co-authored-by: Yoshi Tashiro <[email protected]>
Currently translated at 100.0% (8 of 8 strings) Translation: partner-contact-15.0/partner-contact-15.0-partner_affiliate Translate-URL: https://translation.odoo-community.org/projects/partner-contact-15-0/partner-contact-15-0-partner_affiliate/ca/
|
/ocabot migration partner_affiliate |
|
Sorry @FernandoRomera you are not allowed to mark the addon tobe migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
|
Why are you spamming all your PRs threads if you don't have the permission to mark an addon to be migrated in any of them? |
|
I thought that an action of simply notifying the rest of the community could be done by any contributor. I will not do it again. |
|
No, it's not, as you may overwrite another legitimate pull request with the same migration. That has to be decided by a PSC or the module maintainer. Become maintainer of some modules. |
|
But that is impossible to happen the first time you try to migrate the module. Therefore it would be legitimate, to inform the community of your action, to avoid duplication of work. |
|
Not if you are maintainer on the previous version, but the way to inform that the community is not here, but on the migration issue as centralized place to do that, as for example: #1353 (comment) |
|
This PR has the |
|
/ocabot merge nobump |
|
This PR looks fantastic, let's merge it! |
|
It looks like something changed on |
|
Congratulations, your PR was merged at bcc9c58. Thanks a lot for contributing to OCA. ❤️ |
No description provided.