Dear all

Let me summarize some of the points discussed with Cedric and Dominique
Chabord about the MEDICAL development roadmap and integration to Tryton

Please let's remember that MEDICAL is a project that will work in different
environments (OpenERP and Tryton). With this in mind, let's try to implement
the model that optimizes team work and integration.

- We will be migrating our development environment from SVN to Mercurial as
in MEDICAL 2.0. This would be around December of this year. I believe using
Mercurial will enhance the development process, as well as the integration
with Tryton development.

- In the SVN trunk, today I have already set up and OpenERP and a Tryton
directory. This will help us keep on the parallel development process. We
will start with the Medical core module (medical). Once the core module is
fully functional, we can start parallel migration of the rest of MEDICAL
modules

- 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.

- Documentation : We will start documenting the installation process in the
MEDICAL wiki ( http://sourceforge.net/apps/trac/medical/ )

- 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.

- Bug tracking : We use Mantis at Sourceforge. Should we / how to  integrate
it the current Tryton BTS / code review policies .

- Demo : Dominique Chabord (sisalp) will be hosting demo DBs from MEDICAL
development, both in OpenERP and Tryton environments. Thanks ! Let us know
what you would need.


This is an initial draft. Suggestions and comments will be much appreciated
!


Bests
Luis

-- 
Luis Falcón
http://gnusolidario.org

-- 
[email protected] mailing list

Reply via email to