Do we have any statistics that say how many of our customers are using feature x, feature y, etc.?
If not, I would say if we know about a feature that has regressed to the point of breakage in 4.2 that it should be fixed before releasing (or at the very least well documented, so - if it is impactful to someone - they do not upgrade until it has been fixed). On Mon, Sep 9, 2013 at 2:12 PM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > I think that Animesh is trying to stress what is "key". If it hits 1% of > cloud operators is it key? > > > On 9/9/13 7:42 AM, "Simon Weller" <swel...@ena.com> wrote: > > >-1 from me as well. > > > > > >I know we're trying to hit timed releases, but I think it's very > >important to preserve key underlying functionality across releases. If a > >supported and documented feature is known to be broken, we need to > >address it...if we don't, it's going to cause lots of pain, and reflect > >badly on ACS as a project. > > > >----- Original Message ----- > > > >From: "Chip Childers" <chip.child...@sungard.com> > >To: dev@cloudstack.apache.org > >Sent: Monday, September 9, 2013 9:24:23 AM > >Subject: Re: [VOTE] Apache CloudStack 4.2.0 (fourth round) > > > >On Sun, Sep 08, 2013 at 12:40:30AM -0600, Marcus Sorensen wrote: > >> -1 ... sorry guys, especially with Simon chiming in. > >> > >> I'd request f2c5b5fbfe45196dfad2821fca513ddd6efa25c9 be cherry-picked. > > > >Agreed. > > > >I'm -1, given simon's perspective as well. Since we have the fix, let's > >get it into the release. > > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
