It's not rude in absolut, I know all you explanation. So I have put in the
OpenERP description based in Banking Addons. But I haven't any problem to put
both names. I know the importance of the author, I'm in OpenERP and Opensource
Software since 2007, but my developments are all in the Spanish Localization
Team, this is the first modification in the international community.
About the SEPA files, I understand that it's better have only one module. The
problem it's that in Spain a lot of people use account_payment_extension, so we
need a solution now. So I thinking to make a module that only export SEPA
files, also if you see it I have improved the inheritance.
There are two big problems that can't be not uses banking addons with
account_paytment_extension:
First this:
'conflicts': [
# lp:account-payment/account_payment_extension also adds
# a type field to payment.mode, with a very similar purpose.
# We can't add a dependency on account_payment_extension here
# because account_payment_extension adds many other features
# that probably conflict with other parts of lp:banking-addons.
# Proposal to resolve: make account_payment_extension depend
# on the present account_banking_payment_export module.
'account_payment_extension',
],
Second: banking addons, only export to SEPA in 7.0, in Spain there a lot of
OpenERP 6.0 and 6.1 working.
Greetings
--
https://code.launchpad.net/~openerp-sepa-team/account-payment/account-payment-sepa-6.1/+merge/200480
Your team Account Payment is requested to review the proposed merge of
lp:~openerp-sepa-team/account-payment/account-payment-sepa-6.1 into
lp:account-payment.
--
Mailing list: https://launchpad.net/~account-payment-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~account-payment-team
More help : https://help.launchpad.net/ListHelp
