Re: [Openerp-community] Doubts about how to procced on testing OCA project modules for Odoo
--- Yoshi Tashiro Rooms For (Hong Kong) Limited Phone: +852-3483-1950 Mobile: +852-6682-9005 www.roomsfor.hk www.openerp-asia.net On Jun 14, 2014 8:54 PM, Alejandro Santana alejandrosant...@anubia.es wrote: What about initially placing each module within a folder called __unported__ till each one is verified? (in GitHub) Then, whenever a module is ported and verified for v8, it is moved to project root folder. That has been done in some projects when updating from 6.1 to 7.0 and it is pretty clear and easy to spot which modules hasn't been checked. -- Alejandro Santana alejandrosant...@anubia.es alejandrosant...@anubia.es ~ ANUBÍA, soluciones en la nube, S.L. www.anubia.es http://www.anubia.es/ Plaza Fernando Conde Montero Ríos, 9 36201, Vigo (Pontevedra) 2014-06-14 12:23 GMT+02:00 Ana Juaristi ajuaris...@gmail.com: Hello: We would like to start testing OCA V7 project modules in Odoo and if necesary register bugs and MP proposals. But we have got some doubts about how to procced. 1. Is it better to wait to official Odoo release next 7 July or it's better starting ASAP? 2. Is it better to wait that projects be migrated to Github (I know task is in progress)? 3. Once tested... is someway to mark it has been tested and works in Odoo? Would it better letting modules in V7 repositories and passing to Odoo's ones when they are tested enough and they work? Please we would need some guides to see the better way to procced. Thank you very much: Ana -- CEO Avanzosc, S.L http://www.avanzosc.es : Office phone / Tfono oficina: (+34) 943 02 69 02 Ana Juaristi Olalde http://www.anajuaristi.com/: Personal phone: 677 93 42 59. User/usuario skype: Avanzosc www.openerpsite.com *El contenido de esta comunicación y de toda su documentación anexa es confidencial y se dirige exclusivamente a su destinatario. El uso no autorizado de esta información está prohibido por la legislación vigente. Si usted no es el destinatario le rogamos nos lo indique, no comunique su contenido a terceros y proceda a su destrucción. Disculpe las molestias que le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse para ejercer sus derechos de acceso, rectificación, cancelación y oposición en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 - administrac...@avanzosc.com sopo...@avanzosc.com * *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - **administrac...@avanzosc.com sopo...@avanzosc.com * *This message and all documents attached to it are confidential and intended only for the person or entity to which it is addressed. Any use of this information by unauthorised persons is prohibited under current legislation. If you received this message by error, please advise us, destroy it and refrain from communicating its contents to third parties. We apologise for any inconvenience receiving this email improperly may cause to you. Your personal data are included in a file owned by Avanzosc, S.L. If you want to exercise your rights of access, correction, erasure and objection you can contact the Controller at Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), T: 943 02 69 02 – administrac...@avanzosc.com sopo...@avanzosc.com* ___ 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 ___ 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 ___ 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
Re: [Openerp-community] Doubts about how to procced on testing OCA project modules for Odoo
On Sat, Jun 14, 2014 at 12:08 PM, Alejandro Santana alejandrosant...@anubia.es wrote: Hi, Christian. I think you missunderstood Ana. She is already testing official odoo repo. But she wants to know about testing the different OCA projects (which are not in GitHub yet). As the usual thing to do would be copying a project v7 branch into a v8 branch, and start testing its modules with the last official odoo, fixing once at a time and till tests verify it works with last official odoo version. So she asks if it would be wise to wait till official stable odoo release (2014.07.07), just in case some things change in core. Or maybe it is already a good time to start testing those OCA branches... and how to proceed so everyone knows which modules have been tested with v8 (and fixed, if needed). That is why I suggest the __unported__ folder within each project for the v8-unverified-modules. Thanks Alejandro ! In that way, i recommend migrate repo needed to github if its OCA branch, great ! , work on master branch (trunk in bzr), this will avoid copy paste to work. in git if you has a repo with 7.0 branch stable you can git checkout master and start the work to support 8.0 then checkout -b 8.0 and get the cycle development so clear and fast. Git fashion consider master branch as under development. About risk of changes in core, IMO could be happen but it gives a good feedback and knowhow about core. :-) -- Alejandro Santana alejandrosant...@anubia.es alejandrosant...@anubia.es ~ ANUBÍA, soluciones en la nube, S.L. www.anubia.es http://www.anubia.es/ Plaza Fernando Conde Montero Ríos, 9 36201, Vigo (Pontevedra) 2014-06-14 17:18 GMT+02:00 Ovnicraft ovnicr...@gmail.com: Hi Ana, On Sat, Jun 14, 2014 at 5:23 AM, Ana Juaristi ajuaris...@gmail.com wrote: Hello: We would like to start testing OCA V7 project modules in Odoo and if necesary register bugs and MP proposals. But we have got some doubts about how to procced. 1. Is it better to wait to official Odoo release next 7 July or it's better starting ASAP? You can start ASAP, branch 7.0 is already on odoo repo on github, and it is better test now so you can report issues on github. Here ping to board :-) 2. Is it better to wait that projects be migrated to Github (I know task is in progress)? So would be good if OCA board gives us directives to migrate to github, for example here we need financial reports migrated to github, 3. Once tested... is someway to mark it has been tested and works in Odoo? Would it better letting modules in V7 repositories and passing to Odoo's ones when they are tested enough and they work? Here i missunderstood your question. Please we would need some guides to see the better way to procced. Thank you very much: Ana -- CEO Avanzosc, S.L http://www.avanzosc.es : Office phone / Tfono oficina: (+34) 943 02 69 02 Ana Juaristi Olalde http://www.anajuaristi.com/: Personal phone: 677 93 42 59. User/usuario skype: Avanzosc www.openerpsite.com *El contenido de esta comunicación y de toda su documentación anexa es confidencial y se dirige exclusivamente a su destinatario. El uso no autorizado de esta información está prohibido por la legislación vigente. Si usted no es el destinatario le rogamos nos lo indique, no comunique su contenido a terceros y proceda a su destrucción. Disculpe las molestias que le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse para ejercer sus derechos de acceso, rectificación, cancelación y oposición en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 - administrac...@avanzosc.com sopo...@avanzosc.com * *Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 - **administrac...@avanzosc.com sopo...@avanzosc.com * *This message and all documents attached to it are confidential and intended only for the person or entity to which it is addressed. Any use of this information by unauthorised persons is prohibited under current legislation. If you received this message by error, please advise us, destroy it and refrain from communicating its contents to third parties. We apologise for any inconvenience receiving this email
Re: [Openerp-community] Doubts about how to procced on testing OCA project modules for Odoo
@Nhomar, you are absolutely right for some topics, but the risk of forking too early is that the maintenance cost for including a fix, an enhancement or similar is the double. In spanish localization, to accomodate modules for being 7 and v8 compatible has been a very light task: - Put always from openerp.osv and so on on imports. - Don't use osv.osv for models. - Only one try: .. except: for a concrete module (out of 20). So my theoretical plan is: - Keep the same branch for v7 and v8 until v9 arrives, deprecating some things (like the API). - If some radical changes are introduced for v8, only modules affected by these changes are split in two versions. Technically speaking, I think that this can be supported by git subprojects, but I don't know enough git for now. - When v8 arrives and gets enough traction, if any refactorization is needed, we can think on doing with the new API. - The same can be applied for new developments: evaluate the mass for each version, and decide for which version is convenient to develop it (only v8 with new API and so on, or v7/v8 compatible). Think that having something with only last version compatibility is very cool (because there is an enhancement here and there), but at the end, this functionality must be also for old versions, because not all people migrate to last version (the reasons for this are for another debate). Regards. 2014-06-14 21:42 GMT+02:00 Nhomar Hernández nho...@gmail.com: 2014-06-14 14:41 GMT-05:00 Nhomar Hernández nho...@gmail.com: for v9 also, w I mean v8 also. -- Saludos Cordiales Nhomar G. Hernandez M. +58-414-4110269 Skype: nhomar00 Web-Blog: http://geronimo.com.ve Servicios IT: http://vauxoo.com Linux-Counter: 467724 Correos: nho...@openerp.com.ve nho...@vauxoo.com twitter @nhomar ___ 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
