> I agree with this approach, I don't see any problem. If a later changeset > depends on the faulty one it would be backed out as well, wouldn't it? Yes, you are right.
> We need to put in place a number of automated tests (Functional testing, > DBSourceManager consistency, stability and upgrade; Modularity rules for > minor versions, etc.) as soon as possible. I suggest that release management > prepares the environment and explain to the rest of the community how to > include new test cases in the nigthly build process. This way Release > management overhead won't be a bottleneck, what do you think? This is on the way. Feedback is welcome: http://wiki.openbravo.com/wiki/ERP/Continuous_Integration Thanks, Juan Pablo ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
