info/examples, or explain me how to use
the on_change in trunk ?
Regards,
--
Alexis de Lattre
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-comm
could
test ? I have several modules with on_change to port to 6.1 and I would
like to start the work ASAP.
--
Alexis de Lattre
Le 06/08/2011 19:16, Alexis de Lattre a écrit :
I am starting to work on porting a module (fleet_maintenance) from v5.0
to trunk (6.1). I know that there has been some
mediate"
group to give them such rights.
Regards,
--
Alexis de Lattre
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
Le 11/05/2012 18:08, Alexis de Lattre a écrit :
2. It means that, if you want your sales, purchase or stock users (not
managers) to be able to update a phone number or an email address on a
Partner Address, you will probably think : he needs write access on
Partner Addresses, so I need to add
Dear Christophe,
I had a look at your module "additional_discount" for OpenERP 6.1, and I
was surprised to see that, when you have an "additionnal discount" on an
invoice, it doesn't impact the account move that is generated when you
validate the invoice. You should warn users about this and s
I am the proud author of this great module (!) ; moving it to
lp:account-analytic seems a good idea.
I have noticed that, in lp:account-analytic, the name of all the modules
start with "analytic_"... so should I rename it and remove the
"account_" prefix ? I don't like renaming modules, but if
Le 16/11/2012 16:41, Joël Grand-Guillaume a écrit :
For all of these projects, the rules we expect you to adhere to and
respect are:
*
Nobody merge his/her own work into the branch. Another member of
the team must do it. Exceptions may be accepted if the merge
proposal has been st
Le 14/11/2012 15:34, Stefan Rijnhart a écrit :
as we all know, the current bug policy of OpenERP SA has the following
results:
- Bugs fixed by the community are not applied to the stable version
- Bugs fixed by OpenERP developers through OPW are not merged with the
stable version or after a ve
Le 20/11/2012 15:16, Joël Grand-Guillaume a écrit :
So my question here is, would you all agree to accept the following
people/teams to be part of the new "OpenERP Community Reviewer" ?
- Camptocamp Community Reviewer (Alexandre Fayolle, Guewen Baconnier,
Nicolas Bessi, and me)
- Nhomar Herna
modules written during this code sprint will be published on
https://launchpad.net/openerp-pos (or it's github equivalent).
Regards,
--
Alexis de Lattre
___
Mailing list: https://launchpad.net/~openerp-community
Post to : open
project
The module description told that the two module isn't compatible, but
is possible to make it compatible or is radically different?
They are radically different. You can have a look at the code, it's obvious.
Regards,
Alexis
--
11 matches
Mail list logo