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

[MIG] crm_lead_firstname: Migration to 13.0 #305

Merged
merged 15 commits into from
Mar 18, 2020

Conversation

ntsirintanis
Copy link
Contributor

No description provided.

@rousseldenis
Copy link

@ntsirintanis Could you try to rebase ?

@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch from 4a6f385 to 4ac2635 Compare February 17, 2020 09:14
@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch from 4ac2635 to a8e0b61 Compare February 24, 2020 14:09
@NL66278
Copy link

NL66278 commented Feb 25, 2020

@ntsirintanis Travis fails because of the precommit hook. Please black your code, preferably by using the pre-commit hook from the maintainer quality tools, before submitting again. Runbot fails due to running for more then an hour. This might be caused by other modules running very long to test. Unfortunately there is no detailed log available.

@NL66278
Copy link

NL66278 commented Feb 25, 2020

@ntsirintanis These are the fatal (ERROR) runbot errors:

�[91mERROR: pylint-odoo 0.0.1.dev459 has requirement lxml>=4.2.3, but you'll have lxml 3.7.1 which is incompatible.
�[0m�[91mERROR: coveralls 1.8.2 has requirement coverage<5.0,>=3.6, but you'll have coverage 5.0.3 which is incompatible.

@hbrunn
Copy link
Member

hbrunn commented Feb 25, 2020

@NL66278
Copy link

NL66278 commented Feb 25, 2020

@ntsirintanis and the oca-dependencies.txt file is missing. You can include this from the 12.0 branch as well. This contains the reference to the partner-contact repository.

@ntsirintanis
Copy link
Contributor Author

OK, I'll see into correcting these failing unit tests

@hbrunn
Copy link
Member

hbrunn commented Feb 25, 2020

seems to me you'll have to migrate them to the new form stuff you were struggling with when trying to fix partner_firstname's tests. If you choose your tests wisely, you should be able to circumvent the bug triggered by partner_firstname, as the underlying issue is not yet fixed to my knowledge

@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch from dc75754 to 660e834 Compare February 26, 2020 10:24
@simahawk
Copy link
Contributor

hmm the commits sounds wrong: crm_lead_product is already in v13.
You should:

  1. hard reset on 13.0
  2. cherry-pick your migration commits
  3. fix bugs

@simahawk simahawk changed the title 13.0 mig crm lead firstname [MIG] crm_lead_firstname: Migration to 13.0 Mar 17, 2020
@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch 2 times, most recently from e15d5ba to 12ef0e8 Compare March 17, 2020 10:04
yajo and others added 9 commits March 17, 2020 11:17
This module adds the lastname field to leads and converts current contact name into contact firstname.

Allows to transfer that from and to res.partner objects.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: crm-12.0/crm-12.0-crm_lead_firstname
Translate-URL: https://translation.odoo-community.org/projects/crm-12-0/crm-12-0-crm_lead_firstname/
Currently translated at 100.0% (6 of 6 strings)

Translation: crm-12.0/crm-12.0-crm_lead_firstname
Translate-URL: https://translation.odoo-community.org/projects/crm-12-0/crm-12-0-crm_lead_firstname/de/
badbole and others added 4 commits March 17, 2020 11:17
@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch from 12ef0e8 to 10c1a06 Compare March 17, 2020 10:21
@ntsirintanis
Copy link
Contributor Author

@simahawk thanks a lot for your comments and review! I had mixed up some commits, but this is resolved now. Also fixed unit tests. Let's see if this gets green now.

@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch 2 times, most recently from f694481 to 9ba1e7d Compare March 17, 2020 12:14
@ntsirintanis
Copy link
Contributor Author

@hbrunn @NL66278 @rousseldenis @simahawk LGTM please.

Copy link

@lfreeke lfreeke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional test 👍

Copy link
Member

@hbrunn hbrunn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can add yourself to the contributors

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

Copy link
Contributor

@simahawk simahawk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG, just a bunch of small changes please :)

@ntsirintanis
Copy link
Contributor Author

@simahawk please take another look.

@ntsirintanis ntsirintanis force-pushed the 13.0-mig-crm_lead_firstname branch from a502563 to 33e6383 Compare March 18, 2020 11:35
@simahawk
Copy link
Contributor

/ocabot merge

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 13.0-ocabot-merge-pr-305-by-simahawk-bump-no, awaiting test results.

@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 08184ac. Thanks a lot for contributing to OCA. ❤️

@OCA-git-bot OCA-git-bot merged commit 2253bec into OCA:13.0 Mar 18, 2020
@tonygalmiche tonygalmiche mentioned this pull request May 28, 2020
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.