-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Migration to version 10.0 #117
Comments
I've been testing the refactored v8's version of "letter management" in v10 and everything seems alright providing the creation of "ir.sequence.type" records in "data/letter_sequence.xml" is removed. |
Hi @pedrobaeza , |
@bimajatiwijaya, there are 3 possible ways:
|
Ok thank you @pedrobaeza . |
Would you please remove my name from crm_claim_code module PR: #171 |
PR #180 for crm_claim_type. |
From copyright header? |
I meant with above "Modules to Migration" list. |
Ok, sorry. @bodedra |
Main comment updated. FYI, we have rescued and migrate Odoo's crm_claim module. |
Hi @pedrobaeza , Since the crm_action PR was not continued, we created a new PR #211, migrating directly from the updated module in v9 to include all functionality. Could you update the migration list ? Thanks. |
@gboros-rgbconsulting main comment updated, thanks. |
This is the error that the server show to me in the migration process from the version 8 to the 10 version of the crm_claim module. Lot of thanks, regards. ProgrammingError: relation "crm_team_claim_stage_rel" does not exist |
@tbermudezstm IMHO please create new issue with necessary details and steps. |
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. |
Todo
https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0
Modules to migrate
By @qtheuret - crm_action module migration to v10 #147By @dsidorenkovas-rg - [MIG][10.0] crm_action #211crm_lead_lost_reason - Included in coreThe text was updated successfully, but these errors were encountered: