> This only affects to RM, QA and Rafa. This affects everyone. Starting from the development team and finishing with the end users who report the issues.
Even it it only affected 2 people, it's a key change in our workflow. And it therefore deserves being discussed in calm and well thought and with the rest of team involved (if they want to). I'm sure that all of us will reach to a most satisfactory solution than doing it alone. I'm not discovering a new theory with this, it's the open source philosophy of sharing ideas and improving with the help of all of us. > QA has tried to change this flow > thousands of times even since the beginning when we didn't even agree > with the current solution. Because of lack of resources and because of > lack of technical knowledge on how to change things in Mantis finally we > could never change anything. I'm glad to see that now we can do it > that's why it surprises me that the final solution will come up after > discussing by email and not having a meeting They are not exclusive. There are 2 ways of going to a meeting: with or without preparation. I guess you agree that is better to go after having thought about it. So this thread has been started to put the foundations of what the issue is, what needs to be solved and a possible solution. Then anyone can agree or not with it, propose new ideas, etc. And if after this a meeting is required, for sure it will be a lot more productive than without the previous work. Juan Pablo ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
