-
-
Notifications
You must be signed in to change notification settings - Fork 822
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
9.0 port partner_external_maps #237
Conversation
Travis is red because "Transifex password not recognized- exiting early." ; all the other travis tests are green. |
Please rebase |
aa73628
to
ae3566b
Compare
Rebase done. The file REAME.md is really a pain, because it will always conflict everytime a new module is ported. |
Not if you don't change it. And you mustn't. This is done automatically by an script, so you should abstent to update manually. |
@@ -41,7 +42,11 @@ addon | version | summary | |||
[partner_auto_salesman](partner_auto_salesman/) | 8.0.1.0.0 (unported) | Partner auto salesman | |||
[partner_contact_address_detailed](partner_contact_address_detailed/) | 8.0.1.0.0 (unported) | All address data in summarized contact form | |||
[partner_contact_birthdate](partner_contact_birthdate/) | 8.0.1.0.0 (unported) | Contact's birthdate | |||
<<<<<<< 3398e80890c1e14aa3131baad1a5bf6f9ed6a96b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has not been correctly rebase. Please remove these changes. As stated, they are done automatically after the merge by an script.
Could someone merge this please ? |
@@ -23,7 +23,7 @@ | |||
|
|||
{ | |||
'name': 'Partner External Maps', | |||
'version': '8.0.0.1.0', | |||
'version': '9.0.0.1.0', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
9.0.1.0.0
Some things that I consider before merging:
|
Can you please update the copyright headers to the simple version in all py files following OCA templates |
I think changing the name of the module is a bad idea in most cases (for me, the only good reason to change the name of the module would be if the destination/purpose of the module is radically changed). As the module is kept unchanged, I think we should keep the old name. |
We don't have to extend a firstly badly named module across versions, so we always take the migration as an occasion to change it. Please reconsider your position. |
Well, I don't think that the name is that bad... And if the purpose is only to remove the "s" at the end because some OCA board member had the brillant idea to invent a new "rule" that module names should not have an "s" at the end, then give him some "real" work (porting module to v9 for example) so that he can make himself helpful to the community. In the OCA, we need more guys doing the real work and less people inventing theorical "rules" about every details of modules. |
Hey, the change is not only about the If the problem is the job of renaming, then I can do it. |
In fact, I am in favor of naming conventions, including for module names, but I think that these conventions should apply on new modules only. Changing the name of modules is a pain for users, in particular for non-expert users, for no real benefit. But OK, if you really want to change the name of this module, you can do it. |
Name change and other improvements in akretion#2 |
9 port external maps
Sorry about the lint errors. May I do another PR for fixing them?
|
i fixed them |
Thanks 👍 |
Ready to merge 👍 |
👍 (Code review + functional) |
Contributed by Wim Audenaert.