Hi all, In general I like 2nd approach, so I'll just discuss about it
On 12/02/2010 11:53 AM, Juan Pablo Aroztegi wrote: > * Cons: > > - The 3.0 modules would reside in pi/modules. And the 2.50 modules in > erp/mods. > > - If you want a 3.0 module which is part of the distribution you need > to clone the entire pi repository. For these 2 statements above: would be possible to create a repo in erp/mods per module that is automatically kept in sync with actual sources in pi/modules? Push permissions for this repo would be only for the sync bot, so no pushes allowed for developers, but would allow to clone just a module if wanted. Anyway I don't see a big problem if that is not feaseable as 3.0 modules will depend on core 3.0 I don't really see the case you need to clone a single module without the rest. And you always can use CR to download a published version of any module. > - If we want to develop a new major version of a module included in the > 3.0 distribution, then we'd need to create a separate repository for > that module. I don't get this issue, could you elaborate it a little bit? Other cons/things to keep in mind: -Currently modules directory is in the hgignore, we should ignore all modules but the ones included in pi. -If we follow this approach, would be possible to keep the history of each of the modules? Some more pros: -I really like the idea of creating a new complete repo including all modules for new developments. New developments from now on will typically include changes in several modules so it is great to have all together. -An issue affecting different modules could be solved by a single commit to all of the affected ones, making the commit more readable/compact. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
