Release Criteria

2013-09-10 Thread David Nalley
Hi folks, One of the things I've been pondering of late is a set of release criteria. E.g. here is what CloudStack MUST do to be considered for release. So as background there is a somewhat complex social contract that I think we informally enter with our users. People expect us to release

Re: Release Criteria

2013-09-10 Thread Prasanna Santhanam
On Tue, Sep 10, 2013 at 08:46:43PM -0400, David Nalley wrote: > Hi folks, > > One of the things I've been pondering of late is a set of release > criteria. E.g. here is what CloudStack MUST do to be considered for > release. > > So as background there is a somewhat comp

Re: Release Criteria

2013-09-10 Thread Darren Shepherd
On Tue, Sep 10, 2013 at 9:52 PM, Prasanna Santhanam wrote: > > I think we messed up with the users again this time. Partly a fault > that we can't get beta-quality builds for users to test. Seeing > everyone run 4.2 packages after release announcement and reporting > critical bugs I wish could've

Re: Release Criteria

2013-09-10 Thread Wido den Hollander
On 09/11/2013 07:43 AM, Darren Shepherd wrote: On Tue, Sep 10, 2013 at 9:52 PM, Prasanna Santhanam wrote: I think we messed up with the users again this time. Partly a fault that we can't get beta-quality builds for users to test. Seeing everyone run 4.2 packages after release announcement

Re: Release Criteria

2013-09-11 Thread Sebastien Goasguen
On Sep 11, 2013, at 2:57 AM, Wido den Hollander wrote: > > > On 09/11/2013 07:43 AM, Darren Shepherd wrote: >> On Tue, Sep 10, 2013 at 9:52 PM, Prasanna Santhanam wrote: >> >>> >>> I think we messed up with the users again this time. Partly a fault >>> that we can't get beta-quality builds

Re: Release Criteria

2013-09-11 Thread Dave Cahill
> > > A broken master also slows down other devs. I can't remember the number > of times I've been debugging master for hours to find out something broke > it. > > > so how do we enforce this ? IMO, Gerrit can be used to enforce a saner workflow, see previous discussion at [1]. Having a workflow

Re: Release Criteria

2013-09-11 Thread Wido den Hollander
On 09/11/2013 10:06 AM, Sebastien Goasguen wrote: On Sep 11, 2013, at 2:57 AM, Wido den Hollander wrote: On 09/11/2013 07:43 AM, Darren Shepherd wrote: On Tue, Sep 10, 2013 at 9:52 PM, Prasanna Santhanam wrote: I think we messed up with the users again this time. Partly a fault that

Re: Release Criteria

2013-09-11 Thread Darren Shepherd
Well in the apache model committers are nominated. So basically we should trust our committers. So I'm going to say we enforce this by having good discipline. In really not a fan of adding more process. In communities where gerrit is used its usually done in a model where anybody can commit,

RE: Release Criteria

2013-09-11 Thread Donal Lafferty
> -Original Message- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: 11 September 2013 05:52 > To: dev@cloudstack.apache.org > Subject: Re: Release Criteria > > To get beta quality builds we need to absolutely treat the master branch as > 'sta

RE: Release Criteria

2013-09-11 Thread Alex Huang
> Well in the apache model committers are nominated. So basically we should > trust our committers. So I'm going to say we enforce this by having good > discipline. In really not a fan of adding more process. In communities where > gerrit is used its usually done in a model where anybody can co

RE: Release Criteria

2013-09-11 Thread Animesh Chaturvedi
> -Original Message- > From: David Nalley [mailto:da...@gnsa.us] > Sent: Tuesday, September 10, 2013 5:47 PM > To: dev@cloudstack.apache.org > Subject: Release Criteria > > Hi folks, > > One of the things I've been pondering of late is a set of relea

Re: Release Criteria

2013-09-11 Thread Darren Shepherd
Hmmm... well shoot. If what I'm saying is an argument for gerrit, then I take it back. I don't like heavy processes. Keep it simple, work with good people. Darren On Wed, Sep 11, 2013 at 8:23 PM, Alex Huang wrote: > > Well in the apache model committers are nominated. So basically we > sho

RE: Release Criteria

2013-09-11 Thread Alex Huang
> > > > A broken master also slows down other devs. I can't remember the > number of times I've been debugging master for hours to find out something > broke it. > > > > so how do we enforce this ? > I'm so glad we raise this point. For some time now, Prasanna, Amogh, Frank, and a number of ot

Re: Release Criteria

2013-09-11 Thread Marcus Sorensen
I've repeated it several times in other threads, but I think at a bare minimum it has to work in the listed versions of Ubuntu, CentOS (both mgmt server and KVM host), XenServer, VmWare, what have you, along with the advertised storage and networking. We can discuss limiting that to OSS, maybe, as

Re: Release Criteria

2013-09-30 Thread David Nalley
On Tue, Sep 10, 2013 at 8:46 PM, David Nalley wrote: > Hi folks, > > One of the things I've been pondering of late is a set of release > criteria. E.g. here is what CloudStack MUST do to be considered for > release. > I've spent a lot of time thinking about this -