incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <da...@gnsa.us>
Subject Re: [QA][DISCUSS] Should we document formal release criteria?
Date Tue, 05 Mar 2013 18:39:50 GMT
On Tue, Mar 5, 2013 at 1:32 PM, Chip Childers <chip.childers@sungard.com> wrote:
> Hi all,
>
> Some IRC discussion triggered this thought:
>
> Should we document our formal release criteria?  By that, I mean -
> should we document the criteria that we use to claim that we are in a
> position to cut an actual Release Candidate for voting?
>

YES!!!


> I realized that I've had my own view sitting in my head, but obviously
> that means that nobody else knows it!
>
> Thoughts about what our criteria should be?
>
> Here's what's in my head:
>
> No Blocker Bugs outstanding
> No Critical Bugs outstanding (unless there is a work-around, and only <
> 5 like that)

So define for me what is a blocker and critical.
I have my own internal definition, but if we have a standard that says
'no blocker and critical bugs' then we are just doing blind queries
against Jira and maybe even changing the value on a bug so we can be
releasable.


> Builds all work
> Packaging all works for the selected OS's
> Docs and Translation updates checked in
>
>

Mime
View raw message