[18.0][MIG] pos_payment_change: Migration to 18.0#1453
[18.0][MIG] pos_payment_change: Migration to 18.0#1453
Conversation
Abranes
force-pushed
the
18.0-mig-pos_payment_change
branch
from
0fb2a05 to
4c9439a
Compare
legalsylvain
left a comment
legalsylvain
left a comment
There was a problem hiding this comment.
Diff review. LGTM. Thanks !
|
/ocabot migration pos_payment_change |
|
/ocabot merge nobump |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 18.0-ocabot-merge-pr-1453-by-pedrobaeza-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
|
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 18.0-ocabot-merge-pr-1453-by-pedrobaeza-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
pedrobaeza
left a comment
pedrobaeza
left a comment
There was a problem hiding this comment.
Only OCB is failing due to a tour... let's try again
/ocabot merge nobump
|
This PR looks fantastic, let's merge it! |
|
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 18.0-ocabot-merge-pr-1453-by-pedrobaeza-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
There's no way... |
|
looks like the same as #1455 (comment) |
|
@pedrobaeza could you retry the merge command? Or do you think it will fail again? THX. |
|
I think this will fail while #241122 is not merged. |
|
THX @pedrobaeza . By the way... are you sure that this module is needed in >17.0 ? I see that Odoo has an option for this. Isn't this functionallity included in core? (see screensot). 
And it can be changed using backend options by entering the changes directly in the pos order, as well. |
|
@Abranes @legalsylvain Could you check my comments? THX! |
Currently translated at 100.0% (33 of 33 strings) Translation: pos-16.0/pos-16.0-pos_payment_change Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_payment_change/es/
Currently translated at 100.0% (33 of 33 strings) Translation: pos-16.0/pos-16.0-pos_payment_change Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_payment_change/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pos-16.0/pos-16.0-pos_payment_change Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_payment_change/
Currently translated at 100.0% (33 of 33 strings) Translation: pos-16.0/pos-16.0-pos_payment_change Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_payment_change/es/
Currently translated at 100.0% (33 of 33 strings) Translation: pos-16.0/pos-16.0-pos_payment_change Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_payment_change/fr/
In old version, two certifications modules was present in odoo. l10n_fr_pos_cert and l10n_fr_certification. In odoo 16, only l10n_fr_pos_cert exists.
…e obsolete Warning
Better readme FIX OCA#1115
Abranes
force-pushed
the
18.0-mig-pos_payment_change
branch
from
4c9439a to
0d55ab2
Compare
20 participants
Migration to 18.0 from #1331