cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Chan <will.c...@citrix.com>
Subject RE: [DISCUSS] ACS Release 4 month v/s 6 month
Date Tue, 23 Apr 2013 21:29:36 GMT
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, April 23, 2013 11:19 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] ACS Release 4 month v/s 6 month
> 
> 
> How do you see the release schedule laying out with multiple releases over
> the course of time?  What overlaps exist?
> 
> We *really should not* plan on blocking new features from coming into
> master as they are completed.  That's just an inhibitor to progress.
> Given that assumption, I fail to see how the we would be doing anything
> *but* increasing the overall change size by increasing the time between
> feature releases.  That leads to increased "cost of release".
> 

I'm not saying we should block new features.  I'm simply saying that if a feature is not of
certain quality before we are ready to release, we should consider not including it in the
release notes.  For example, the bare metal feature was something written by Frank just before
he personally went on a month long vacation.  I'm sure the community may have been able to
help him out but without his help in such a short release cycle, the community IMO did the
right thing and did not deem this feature GA for 4.1.  With a longer test/fix cycle, either
Frank could have come back in time to help OR the community may have *learned* enough of the
feature to fix those issues.  In any case, this is simply one example and even I wouldn't
simply use this case as the only example to why we should increase the QA/Fix time.

Also, as I said previously, it takes more than 3 months from the time it takes to code freeze
on a CCP major release to the time where we are comfortable to GA it.  Now, of course ACS
does not require the quality of CCP but on the other hand, our process here allows me to effectively
ensure that certain bugs and QA tasks are done according to a tight schedule.  ACS does not
have this luxury.

Also, I do see more patch/maintenance releases coming out in between major releases.  We will
quickly find out that there the cadence would be too fast.

Will

Mime
View raw message