cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: [VOTE] Apache CloudStack 4.0.2
Date Wed, 17 Apr 2013 15:04:28 GMT
It's a little more nuanced than that. ;) It's very possible that we would
ship a new release that actually introduces known bugs. It is much less
likely that we would ship a release that introduces known critical bugs. In
the end, it is up to the community to decide. And that is a process of a
release manager making the cut, and calling the vote. And then we use our
by-laws and voting rules to decide what we do! :)


On 17 April 2013 15:49, Marcus Sorensen <shadowsor@gmail.com> wrote:

> OK, so the answer is no, we just decide as we go...
> On Apr 17, 2013 8:15 AM, "Chip Childers" <chip.childers@sungard.com>
> wrote:
>
> > On Wed, Apr 17, 2013 at 08:11:38AM -0600, Marcus Sorensen wrote:
> > > Do we have rules set out around this? It seems that we wouldn't stop a
> > > time-based bug fix release from going out just because it doesn't fix
> > every
> > > bug we know of, only if it introduces a bug.
> >
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Apache+CloudStack+Project+Bylaws#ApacheCloudStackProjectBylaws-3.DecisionMaking
> >
> > Section 3.4.3. - Lazy Majority of PMC
> >
> >
>



-- 
NS

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message