Juan Pablo, Dmitry, Peter, Pablo, Rafa and all, I am not sure to fully understand the root cause of this emails, I am plenty sure Juampa's idea of sharing his thoughts about the change to the rest of us was a great idea. As Juampa said, we believe that sharing ideas is good, so this brain-storming-like thread could be positive for us as a company. I do not fully agree with starting a discussion, in the "I don't agree with you / me neither" way. I think it is much better if anyone could make his position in a constructive way avoiding direct confronting. And, of course, once everyone has stated his point of view, Management could hold a meeting with significant stakeholders in order to get a final decision.
Now, regarding the original subject. Juampa, it woud be great if you tell us a little more about how the change affects each role according the current flow [1]. As far as I understand, it is transparent for a Reporter, and Triage Team is not affected neither. But I am not sure what are the expected changes for the rest. And one more question, will this affect the SLAs? Regards, PL [1] http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#The_Issue_Life_Cycle Juan Pablo Aroztegi wrote: >> 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 > ------------------------------------------------------------------------------ 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
