-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
[14.0] Migration: l10n_it_esigibilita_iva #1938
[14.0] Migration: l10n_it_esigibilita_iva #1938
Conversation
Esigibilità iva su conto imposta payability moved to account tax
Currently translated at 100.0% (5 of 5 strings) Translation: l10n-italy-11.0/l10n-italy-11.0-l10n_it_esigibilita_iva Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-11-0/l10n-italy-11-0-l10n_it_esigibilita_iva/it/
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_esigibilita_iva Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_esigibilita_iva/
Currently translated at 100.0% (5 of 5 strings) Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_esigibilita_iva Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_esigibilita_iva/it/
# License LGPL-3.0 or later (http://www.gnu.org/licenses/lgpl). | ||
|
||
{ | ||
"name": "Italian Localization - Esigibilita' IVA", |
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.
Puoi cogliere l'occasione per adattarlo a https://www.odoo-italia.org/documentazione/12.0/sviluppo/guidelines.html#titolo-del-modulo ?
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.
Il passaggio alla 14.0 potrebbe essere l'occasione giusta per uniformare i nomi dei moduli e portare in inglese i pochi rimasti in italiano. In questo caso l10n_it_vat_payability.
Questo anche in ottica di collaborazione più ampia a livello internazionale (anche con Odoo S.A. ad esempio).
Che ne pensate @OCA/local-italy-developers @OCA/local-italy-maintainers ?
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.
@primes2h +1
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.
Sono a favore. Mi chiedo però se abbia senso anche prevedere uno script di migrazione o una procedura simile a quella descritta in https://github.com/OCA/l10n-italy/blob/12.0/l10n_it_invoices_data_communication/README.rst#known-issues--roadmap in modo da ripulire i dati che fanno riferimento al vecchio nome.
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.
@tafaRU Completamente d'accordo sul dettagliare la parte della migrazione
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.
Bisogna capire come poter testare lo script di migrazione. A tal proposito incollo il link all'inizio della discussione affrontata sul canale Discord: https://discord.com/channels/753902328494424064/753902328494424070/802132198555516959
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.
Qualcuno può chiedere consiglio su [email protected] ?
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.
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.
Qui c'è un esempio pratico di una variazione del nome di un modulo nella migrazione alla v.13.0.
È partito tutto da qui OCA/manufacture#481 (comment)
Questa la PR OCA/manufacture#595 nella quale non hanno inserito script di migrazione (*) ma questo commento di Pedro mi sembra importante OCA/manufacture#595 (comment)
(*) forse la gestiscono direttamente in OpenUpgrade?
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.
Per completezza, visto che su https://odoo-community.org/groups/contributors-15/contributors-185922 non si legge, riporto la risposta di Holger:
In general, is it possible to test v14 upgrade scripts before OpenUpgrade is
available for v14?
yes, you don't need OpenUpgrade for that.
We lack a good mechanism to test migration scripts, I'm also not sure how I
would implement such a thing in general. The specific script looks a bit
pointless to test to me, but you could mock the openupgradelib calls and call
the function if you're into coverage
628ab40
to
cb67981
Compare
cb67981
to
d1437a3
Compare
85e59f9
to
c4863a1
Compare
c4863a1
to
6036453
Compare
Congratulations, your PR was merged at c5f84d5. Thanks a lot for contributing to OCA. ❤️ |
Porting del modulo l10n_it_esigibilita_iva dalla versione 12.0 alla 14.0
--
Confermo di aver firmato il CLA https://odoo-community.org/page/cla e di aver letto le linee guida su https://odoo-community.org/page/contributing