On 22/05/11 13:04 -0300, Luis Falcon wrote: > - Versioning : MEDICAL has its own versioning. The same version applies for > different Tryton or OpenERP environments. Each medical version will contain > a set of modules. The core module (medical) will have the proper > documentation about installation in OpenERP and Tryton. This documentation > also includes the relationship with MEDICAL version and the required OpenERP > and Tryton counterpart.
So you will be able to use the numbering of Tryton for modules. Per example, Medical 2.0 will be composed of a set of modules for Tryton 2.2: trytond_medical-2.2.0, trytond_medical_genetics-2.2.1, trytond_medical_gyneco-2.2.3 etc. And the Medical 2.0 for Tryton 2.0: trytond_medical-2.0.0, trytond_medical_genetics-2.0.1 etc. Like that, you will be able to re-use the generic setup.py already used in Tryton's modules. > - Translation : We are currently using Transifex for translating MEDICAL. It > works quite nice, but we have to see how to unify all the translation terms > in both xml and csv. Tryton uses a custom csv format. But it could be the opportunity to implement the po parsing I talk about in https://bugs.tryton.org/roundup/issue1163 Also I think it will be possible to write a script to sync translation between both backend version. > - Bug tracking : We use Mantis at Sourceforge. Should we / how to integrate > it the current Tryton BTS / code review policies . I think it is better that Medical continues to use his own bug tracker because I guess most of the time fix will need to go on both side (Tryton and OE). About codereview, I think it will be good for Medical to use http://codereview.tryton.org/ to review Tryton version of modules because the most Tryton developers review the code, better it will be. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpyfBdY8MDxS.pgp
Description: PGP signature
