A clarification on this measure: * Only commits fixing the integration can be pushed. * If you have a commit which is a showstopper for MP1, you can push it. * If you have a commit which is a very nice to have for MP1, you must not push it.
Juan Pablo On Mon, Jul 4, 2011 at 9:51 AM, Juan Pablo Aroztegi <juanpablo.arozt...@openbravo.com> wrote: > Hi all. It's been 9 days since the last promotion. Given that want to > freeze MP1 any time soon, we're going to do a logical freeze in pi to > make sure we fix the integration. > > Currently the problem is that the module installation test doesn't > work, so we're unable to make progress. This issue has the highest > priority: > https://issues.openbravo.com/view.php?id=17872 > > Until further notice only those people who are told to fix an > integration issue should push commits to pi. Hopefully this shouldn't > last long. As usual, please remember that "try" is a tool you can use > to considerably reduce these kind of undesirable situations. > > > > Thank you, > > Juan Pablo > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
