One thought is if a feature is not nearing test completion then considering pushing it out to next release and move the corresponding bugs as well out of 4.4
Thanks Animesh > -----Original Message----- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Monday, June 16, 2014 11:21 PM > To: dev > Subject: Re: [ACS44] are we RC-ready? > > I know some of them are not, but a lot may be. We all need to have a look > at that. I will, but the total number is over 350! (including those not marked > as critical.) > > On Mon, Jun 16, 2014 at 10:02 PM, Animesh Chaturvedi > <animesh.chaturv...@citrix.com> wrote: > > 84 is a bug number to call RC ready unless the issues are not really > > critical > > > >> -----Original Message----- > >> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > >> Sent: Monday, June 16, 2014 7:11 AM > >> To: dev > >> Subject: [ACS44] are we RC-ready? > >> > >> s far as I can tell the only remaining blocker issue has been fixed last > week. > >> There are 84 criticals. Do we feel we are RC ready as we are or are > >> some of those critical to critical to go and release? If so, what > >> needs to be done to get there. Please respond promptly or show > >> yourself on #cloudstack- meeting in 50 minutes. > >> > >> with kind regards and loads of gratitude, > >> -- > >> Daan > > > > -- > Daan
