The promotion from pi to main and the Central Repository is already in place. Here's a high level explanation of how it works, and some consequences that directly affect you:
* If a changeset passes all the tests, we promote the code to main. As usual. * At the same time we build the modules that have been changed by those changesets and we publish them to the CR in the "Test" maturity level. This means that every time there's a promotion people willing to test the latest development version can do so by using the Module Management Console. There's no need to have a development environment any more (for non-developers, I mean). * Every time there's a promotion to main we set the minor version numbers for the modules that change. This means that from now on developers must never change the minor version of the modules included in pi. They can, however, change the major versions whenever it's necessary. * Finally, every time there's a promotion to main we'll also merge those changesets back to pi. Because otherwise there could be a module version dependencies disaster and the CR would not accept our new modules. Should you have any questions about this, feel free to ask them here. Regards, Juan Pablo ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
