> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, April 22, 2013 2:20 PM
> To: cloudstack-...@incubator.apache.org
> Subject: [DISCUSS] ACS Release 4 month v/s 6 month
>
> Folks
>
> We started discussing 4 month v/s 6 month release cy
r.apache.org
> Subject: RE: [DISCUSS] ACS Release 4 month v/s 6 month
>
>
>
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Monday, April 22, 2013 2:20 PM
> > To: cloudstack-...@incubator.apache.org
> &
Sent: Monday, April 22, 2013 4:08 PM
>> To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
>> Subject: RE: [DISCUSS] ACS Release 4 month v/s 6 month
>>
>>
>>
>> > -Original Message-
>> > From: Animesh Chaturvedi [mailto:animesh
Animesh
I personally believe 4 months cycle is too rapid and we need more time to Qa
and fix all issues.
I'm finding issues constantly that automated tests missed.
My opinion, we should release a stable product when it's ready, hopefully
following a 6 months cycle.
Regards
Ilya
Given the remaining work to reshape CloudStack into a better architecture
to response other "Stacks" (i.e., OpenStack) at architecture level in
addition to feature development. I prefer a 6 month release cycle.
Kelven
On 4/22/13 4:47 PM, "Musayev, Ilya" wrote:
>Animesh
>
>I personally believe 4
On Mon, Apr 22, 2013 at 5:19 PM, Animesh Chaturvedi
wrote:
> Folks
>
> We started discussing 4 month v/s 6 month release cycle in a another thread
> [1]. Since the subject of that thread was different, community may not have
> participated in this important discussion fully. I am are bringing t
+1, on the automation test. When will we have good automation test?
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Monday, April 22, 2013 7:52 PM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISC
+1 for 6 month cycle till Automation is in place and current backlog of defects
are reduced. Once we have automation we can switch to shorter cycles
May be having release goals set to meet this criteria ( % of backlog to be
cleared + %age of automation to be achieved) might help to reduce the cy
: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Tuesday, April 23, 2013 4:38 AM
To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
Subject: RE: [DISCUSS] ACS Release 4 month v/s 6 month
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chatur
: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Tuesday, April 23, 2013 4:38 AM
To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
Subject: RE: [DISCUSS] ACS Release 4 month v/s 6 month
> -Original Message-
> From: Animesh Chat
David - You have some compelling logic :)
Given the debate about 4 month to 6 month, lets make an educated decision
First - Lets hear from the "release managers" as to what they have to say
about the last 2 releases. What went well and what didn't. Chip - ?
Second - If we plan to do a 6 month rele
On Apr 23, 2013, at 1:32 AM, Nitin Mehta wrote:
> David - You have some compelling logic :)
> Given the debate about 4 month to 6 month, lets make an educated decision
>
> First - Lets hear from the "release managers" as to what they have to say
> about the last 2 releases. What went well and w
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org; Chip Childers
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
>
> On Apr 23, 2013, at 1:32 AM, Nitin Mehta wrote:
>
> > David - You have some compelling logic :) Given the debate about 4
> > m
On Mon, Apr 22, 2013, at 04:19 PM, Animesh Chaturvedi wrote:
> - Joe agrees partly in release overhead being significant for major
> release
This is only a partial summary of what I've said before. Yes, I think
there's overhead in a release that's really non-flexible.
However, we've really not
The problem (I am beginning to realize) with extending the release is
the temptation to cram in more features. May be use the collab
conference to improve release management aspects. What we did right
in 4.1, what went wrong, how to better plan 5.0. And that can happen
with a 4 or 6 month cycle. I
nt: Monday, April 22, 2013 7:52 PM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
> On Mon, Apr 22, 2013 at 5:19 PM, Animesh Chaturvedi
> wrote:
> > Folks
> >
> > We started discussing 4 mont
ier.
>
> Cheers,
>
> Hugo
>
> > -Original Message-
> > From: Sebastien Goasguen [mailto:run...@gmail.com]
> > Sent: Tuesday, April 23, 2013 9:31 AM
> > To: dev@cloudstack.apache.org
> > Cc: cloudstack-...@incubator.apache.org; Chip Child
On Tue, Apr 23, 2013 at 10:55:50AM -0700, Will Chan wrote:
> Again, I am not disputing that more features will make it in given Dave's
> argument. In fact, I'm not really that keen on using the fixed cost of
> release mgmt. for the reason of the move as well. Heck, I'm not even sure a
> 6 mon
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, April 23, 2013 11:19 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
>
>
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, April 23, 2013 11:19 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
> On Tu
Subject: RE: [DISCUSS] ACS Release 4 month v/s 6 month
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, April 23, 2013 11:19 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISC
I side with Dave and Chip on this one. The 4 month dev cycle has forced
CloudStack to own up to its problems in planning, testing, and automation.
Until that has been settled, going to a longer release cycle is actually not
beneficial to this community.
--Alex
> -Original Message-
>
I see where David is coming from.
The longer you leave a release branch, the harder it becomes to QA, the
harder it comes to test, and the harder it becomes to release. As has been
mentioned already, you can think of this as a "release cost". More regular
releases keep complexity down, and reduce
On Wed, Apr 24, 2013 at 12:22:58PM +0100, Noah Slater wrote:
> I see where David is coming from.
>
> The longer you leave a release branch, the harder it becomes to QA, the
> harder it comes to test, and the harder it becomes to release. As has been
> mentioned already, you can think of this as a
s etc. on Monday
Thanks
Animesh
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, April 25, 2013 9:24 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
> On Wed, Apr 24, 2013
On Thu, Apr 25, 2013 at 05:02:05PM -0700, Animesh Chaturvedi wrote:
> Let me attempt to summarize this thread, if I missed any glaring points feel
> free to bring them up
>
> 4 months:
> Proponents (9): Chip, Alex, David, Noah, Hugo, Joe, Sebastian, Prasanna,
> Rohit
> Reasoning:
> * We hav
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, April 25, 2013 5:11 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
>
> On Thu, Apr 25, 2013 at 05:02:05PM -0700, Animesh Chat
On 26 April 2013 05:32, Animesh Chaturvedi
wrote:
> Let me attempt to summarize this thread, if I missed any glaring points feel
> free to bring them up
>
> 4 months:
> Proponents (9): Chip, Alex, David, Noah, Hugo, Joe, Sebastian, Prasanna,
> Rohit
> Reasoning:
> * We have not given prop
Thanks for the great summary Animesh. Agree with Chip. Great thread. :)
On 26 April 2013 01:11, Chip Childers wrote:
> On Thu, Apr 25, 2013 at 05:02:05PM -0700, Animesh Chaturvedi wrote:
> > Let me attempt to summarize this thread, if I missed any glaring points
> feel free to bring them up
> >
29 matches
Mail list logo
