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.

Sign up for GitHub

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

Jump to bottom

Migration to version 11.0 #482

Closed
37 of 53 tasks
pedrobaeza opened this issue Oct 3, 2017 · 32 comments
Closed
37 of 53 tasks

Migration to version 11.0 #482

pedrobaeza opened this issue Oct 3, 2017 · 32 comments
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Milestone
11.0

Comments

@pedrobaeza
Copy link
Member

pedrobaeza commented Oct 3, 2017 •
edited by NL66278
Loading

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-11.0

Modules to migrate
@pedrobaeza pedrobaeza added this to the 11.0 milestone Oct 3, 2017
@feketemihai
Copy link
Member

feketemihai commented Oct 19, 2017 •
edited
Loading

partner_create_by_vat will not be migrated, Odoo's module "base_vat_autocomplete" is doing the same things...should i do something else since the module will be deprecated?

@pedrobaeza
Copy link
Member Author

OK, noted

@njeudy
Copy link

njeudy commented Oct 24, 2017

@pedrobaeza : partner_contact_in_several_companies and partner_contact_personal_information_page

#507

@bouvyd
Copy link

bouvyd commented Oct 30, 2017 •
edited
Loading

Seems like partner_company_type does mostly the same thing as res.partner.industry model introduced in 11.0 at odoo/odoo@9a572f8

I'll leave you the judge of that though

Edit: perhaps it's actually partner_sector that is impacted. Honestly not sure about the functional difference between those two.

@jprobineau
Copy link

@pedrobaeza : partner_contact_birthdate, partner_contact_gender, partner_contact_nationality, partner_contact_personal_information_page

@emagdalenaC2i
Copy link
Contributor

@dbo-odoo I agree, partner_sector is like res.partner.industry introduced in Odoo 11. You can manage the sectors / industry types in: Contacts --> Configuration --> Sectors of activity

@yajo
Copy link
Member

yajo commented Nov 14, 2017

Then it should get migrated by OpenUpgrade possibly.

@pedrobaeza
Copy link
Member Author

Well, there's no 1:1 feature mapping, as parner_sector includes a many2many field for indicating secondary sectors, and also the included sector in standard data is not what everyone can consider as their current sectors. To be investigated further...

@astirpe
Copy link
Member

astirpe commented Nov 28, 2017

The functionality provided by module partner_street_number is completely covered by standard module base_address_extended.

Can we remove partner_street_number from the list of modules to be ported?

@pedrobaeza
Copy link
Member Author

We should analyze it then in OpenUpgrade for a smooth migration from v10 partner_street_number to v11 base_address_extended. Any way, I strike-through the line.

@simahawk
Copy link
Contributor

simahawk commented Nov 29, 2017 •
edited by pedrobaeza
Loading

partner_identification @simahawk #526

@jesusVMayor
Copy link
Member

base_partner_sequence #531

@JayVora-SerpentCS
Copy link
Contributor

partner_auto_salesman #542

@JayVora-SerpentCS
Copy link
Contributor

base_partner_merge #545

@JayVora-SerpentCS
Copy link
Contributor

portal_partner_merge #546

@astirpe
Copy link
Member

astirpe commented Jan 22, 2018

base_vat_sanitized #552

@andreschenkels
Copy link
Member

It seems like most migrations to v11 stopped for partner-contact anything I can do here?

@pedrobaeza
Copy link
Member Author

Well, if you are interested in any module, you can:

  • Review the PR if it's already proposed.
  • Migrate a module and propose a PR.

@ddufresne
Copy link
Contributor

I would like to contribute on the migration of partner_multi_relation. I could do this tomorrow.

@NL66278 have you already begin at Therp ?

@NL66278
Copy link
Contributor

NL66278 commented Feb 22, 2018

@ddufresne We have not started migration to 11.0, but we still have an outstanding PR for 10.0 that has a refactoring for easier extention. If you migrate, I would suggest to take that as a starting point. #497

@ddufresne
Copy link
Contributor

@NL66278 sure, already gave my thumbs up for the refactoring. I will start from there.

@ddufresne
Copy link
Contributor

partner_multi_relation #564

@astirpe
Copy link
Member

astirpe commented Jul 19, 2018

partner_coc #611

@NL66278
Copy link
Contributor

NL66278 commented Nov 27, 2018

@pedrobaeza partner_contact_gender now migrated here: #662. There is a message about Yairo Llopez not having signed the CLA, but this is about existing code already merged in other branches. Besides that, I think it is more of a problem of changed email or something like that.

@pedrobaeza
Copy link
Member Author

About the CLA claim, it's because the CLA bot has been reworked recently because it was not working correctly, so maybe some missing CLAs that weren't detected previously are now claimed. There's also another fact: on v6.1/v7, when OCA started, there was a massive dump of existing module from openerp-extra mega-repository without claiming the CLA, and now as we are importing full commit history, this might arise again. Don't worry about that, and we will normalize missing CLAs step by step.

@emagdalenaC2i
Copy link
Contributor

partner_contact_personal_information_page - By @jprobineau - #511 is closed and superseded By @njeudy - #507 that is already merged (there are the migration of partner_contact_personal_information_page and partner_contact_in_several_companies in the same PR)

Please, check in the list partner_sector - By @mreficent - #619 because it is already merged and renamed as -> partner_industry_secondary

check in the list partner_contact_lang - By @cristinamartinrod - #636

Please add to the list partner_ref_unique - By @cristinamartinrod - #626 that is already migrated and merged

There is a PR for the migration of partner_company_type - By @daramousk - #660

Please, add to the list partner_noncommercial - By @lfreeke - #657

Please, add to the list partner_email_check - By @denislour - #543

Please, add to the list partner_contact_role - By @simahawk - #524

Please, add to the list base_continent - By @awwea - #523

@luismontalba
Copy link
Member

It seems that partner_contact_configuration is not needed in V11 because these menus are included in the contacts module in core, and they are available for any user included in group base.group_system

@pedrobaeza
Copy link
Member Author

OK, thanks for noting it

@luismontalba
Copy link
Member

partner_academic_title migrated in #719

@emagdalenaC2i
Copy link
Contributor

Please, check partner_academic_title - By @luismontalba - #719 that is already merged

@NL66278
Copy link
Contributor

NL66278 commented Dec 11, 2020

Unfortunately partner_street_number is not completely covered by base_address_extended, as in that module the street fields are not split for contacts in the main partner form...

@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Projects
None yet
Milestone
11.0
Development

No branches or pull requests