cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebgoa <run...@gmail.com>
Subject Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze
Date Fri, 30 May 2014 12:26:00 GMT

On May 29, 2014, at 9:34 PM, Mike Tutkowski <mike.tutkowski@solidfire.com> wrote:

> In an effort to help keep our releases from getting out of hand, I think we
> should consider moving the Feature Proposal deadline up, as well.
> 
> My main concern is that many people have three CloudStack-related "threads"
> executing right now, though:
> 
> 1) People are still testing 4.4.
> 
> 2) People are developing for 4.5.
> 
> 3) People are now expected to think in detail earlier about the features
> they'd like to place in 4.6.

And 4.3 bugs are not being fixed...

> 
> 
> On Thu, May 29, 2014 at 12:58 PM, Daan Hoogland <daan.hoogland@gmail.com>wrote:
> 
>> That is what I want with this thread, yes. Please counter propose or
>> amend as you like.
>> 
>> On Thu, May 29, 2014 at 8:11 PM, Marcus <shadowsor@gmail.com> wrote:
>>> Perhaps we need to review/replace the release plan as a whole, find
>>> something that will get us on track and keep us on track.
>>> 
>>> 
>>> On Thu, May 29, 2014 at 11:45 AM, Daan Hoogland <daan.hoogland@gmail.com
>>> 
>>> wrote:
>>> 
>>>> Seeing what objections there might be I want to amend my proposal to
>>>> 
>>>> 1. move forward feature freeze not on the coming but on the next
>> release.
>>>> 2. set feature proposal dealine for the coming release on 19th of June
>>>> 
>>>> flames? other thoughts?
>>>> Daan
>>>> 
>>>> On Wed, May 28, 2014 at 8:17 AM, Ritu Sabharwal <rsabharw@brocade.com>
>>>> wrote:
>>>>> Thanks Daan for the clarification!
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
>>>>> Sent: Tuesday, May 27, 2014 1:56 PM
>>>>> To: dev
>>>>> Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze
>>>>> 
>>>>> What I mean is that to prevent the date of oct '14 moving we need to
>>>> move the feature freeze forward. so we have more time to create the
>> release.
>>>>> 
>>>>> On Tue, May 27, 2014 at 10:45 PM, Ritu Sabharwal <
>> rsabharw@brocade.com>
>>>> wrote:
>>>>>> When  you say release schedule shift, does it mean 4.5 release target
>>>> is moved from Oct '14 to a forward date?
>>>>>> 
>>>>>> Thanks & Regards,
>>>>>> Ritu S.
>>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
>>>>>> Sent: Monday, May 26, 2014 5:26 AM
>>>>>> To: dev
>>>>>> Subject: [ACS45][ACS50][PROPOSAL] move forward feature freeze
>>>>>> 
>>>>>> LS,
>>>>>> 
>>>>>> When I seeing once again our release schedule shift, I think we have
>> no
>>>> option but to move feature freeze for the next release forward.
>>>>>> This is the only way it seems we can reduce the complexity of the
>> total
>>>> sum of changes. Therefore it is the only way we can prevent lapsing even
>>>> more in time without risking reduced quality of our next release.
>>>>>> So I propose to move feature freeze forward by a month to be at the
>>>> 19th of June (instead of July). I don't think we need to strictly move
>> code
>>>> freeze forward as well but vigilance onto added features will be
>> necessary.
>>>>>> 
>>>>>> --
>>>>>> Daan
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Daan
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Daan
>>>> 
>> 
>> 
>> 
>> --
>> Daan
>> 
> 
> 
> 
> -- 
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*


Mime
View raw message