RE: [ACS42] Issues that are resolved but not closed yet

2013-07-15 Thread Animesh Chaturvedi
> To: dev@cloudstack.apache.org > Subject: [ACS42] Issues that are resolved but not closed yet > > We have large number of issues (510) that are resolved but not closed > yet. Here is the list by reporter. Please review the issues and help > bring them to closure. > > Abhinanda

Re: [ACS42] Issues that are resolved but not closed yet

2013-07-12 Thread Chip Childers
On Fri, Jul 12, 2013 at 11:59:29PM +0530, Rohit Yadav wrote: > +1 what Chip suggests. Developers will have a habit to see the ticket > they're assigned. > You can actually automate this by forking my RBTool fork [1] for your > benefit (idea would be write a tool for Release managers to keep a track

Re: [ACS42] Issues that are resolved but not closed yet

2013-07-12 Thread Chip Childers
Perhaps use a mass-update of these tickets to simply add a comment asking for validation and closure? On Fri, Jul 12, 2013 at 06:23:46AM +, Animesh Chaturvedi wrote: > We have large number of issues (510) that are resolved but not closed yet. > Here is the list by reporter. Please review the

[ACS42] Issues that are resolved but not closed yet

2013-07-11 Thread Animesh Chaturvedi
We have large number of issues (510) that are resolved but not closed yet. Here is the list by reporter. Please review the issues and help bring them to closure. Abhinandan Prateek CLOUDSTACK-2321 Fix the response of scaleVMCmd CLOUDSTACK-3136 Support for "Ubuntu