Pablo I think this is the perfect place to discuss this. The more audience the better, after all this is a process that contains no business secrets and affects the workflow of many.
Best regards, Peter On 18.11.2009, at 23:01, PSarobe wrote: > I would like to discuss this in private. I don't think this is the best > place. > > Regards > --- > Sent via BlackBerry > > -----Original Message----- > From: Juan Pablo Aroztegi <[email protected]> > Date: Wed, 18 Nov 2009 20:58:57 > To: <[email protected]> > Subject: Re: [Openbravo-development] QA status in the issue tracker > > Hi Dmitry, > >> My suggestions are: >> 1. To change new status names. Currently status reflects the work done like >> Scheduled, Resolved. >> So >> * Ready for testing --> Fixed (it will be in line with the current comments >> we have from mercurial when the change is done and a bit more marketing >> friendly :-) >> * Ready for review --> Auto Tested. > I don't agree with this part. "Fixed" and "Auto Tested" require extra > explanations. One could quickly ask what's the difference between "Fixed" > and "Resolved", it's far from being obvious. "Ready for testing" and > "Ready for review" are self explanatory. I'm specially against "Fixed", > because it's simply false. > > It is true that "Ready for review" does not reflect the > work done, but we also have "Feedback", which also doesn't. I mean, there > are many other typical useful statuses in issue trackers, like "Waiting > Approval" or "Awaiting Info" (=feedback) which do not follow the "work > done" logic and I don't see a reason why they should. > > In any case we agree on the concept and that's the important part. > >> 2. We have automatic promotion to main so we can start implementing new >> "Ready >> for review (Auto Tested)" status but transfer issue further the same way we >> do right now (so that from "Ready for review" directly to "Closed" and >> manually)*.* > Moving an issue from "Resolved" to "Closed" doesn't have to be automatic > from the 1st day I think, because only RM is involved in this process and > it's a 5min task to mark all the issues. > > > Thanks, > > 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 ------------------------------------------------------------------------------ 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
