cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <>
Subject Re: [DISCUSS] releases going forward
Date Mon, 10 Dec 2012 18:43:59 GMT
On Sat, Dec 1, 2012 at 7:12 PM, Noah Slater <> wrote:
> Late to the party here folks, and this may have been covered in one of the
> other threads about releasing. Automation is great. But all we can automate
> is the preparation of release candidates. But the voting will always be
> manual, and will always take 72 hours or more.
> So the question shifts to: how often do you want to spam the dev list? How
> often can the community be reasonably be expected to download the release
> candidate and go through all of the tests?

Let's not confuse the testing process that this community goes through
*before* proposing a release with the act of testing the release
candidate.  We are talking about automating the test process prior to
cutting an RC.

CloudStack requires a significant amount of infrastructure to test
completely, and has a fairly large test suite (mostly manual from my
discussions with Sudha at the conference) with which many of the test
engineers involved help us ensure that we are going to be starting
from a code branch that has a high level of functional quality .  We,
as a community, are trying to figure out how to significantly decrease
the time it takes for the test engineering community members to go
through that process.  This, in turn, will speed up the test/fix cycle
leading up to the start of RC testing.

Responding to the vote is a whole different story, and not directly
the point of all of the test automation that's being discussed
(although it might very well benefit from more automated tests as


> On 10 November 2012 07:44, Rohit Yadav <> wrote:
>> This is something I want, a rolling release model (like Arch or Gentoo)
>> where we can do releases based on automated QA frequently say every week or
>> month and do major releases every 2-5 months (or whatever timelines we
>> decide) as discussed which would be both manual and automated QA-ed. The
>> automation in QA using DevCloud and our test infra. would get us there.
>> Regards.
>> ________________________________________
>> From: David Nalley []
>> Sent: Saturday, November 10, 2012 3:37 AM
>> To:
>> Cc: Rohit Yadav; Childers
>> Subject: Re: [DISCUSS] releases going forward
>> > I am no release expert, but I was at couple devops events lately and the
>> continuous delivery model makes sense to me. We should aim to be able to
>> release "every day".  Automate everything up to the actual vote. The manual
>> vote should actually be the lengthiest process in the release. With that
>> concept, aiming at a release every week would be the optimal (I know this
>> is silly !!)
>> > A search on Release early, release often leads to
>>, nice
quick read.
>> I agree - Continuous Delivery is an awesome read btw. I'd love to be
>> in that state, and folks like Prasanna are actively working on getting
>> us there.
>> >
>> > In general I think we should release first and fix later, rather than
>> fix and release.
>> >
>> > Have we cut 4.0.1 yet ?
>> Nope, but we should start talking about it soon. There are a number of
>> bugs that seem ideal candidates, some of which have been fixed
>> already.
>> >
>> > I will go back to my guinness now :)
>> >
>> > -Sebastien
>> >
> --
> NS

View raw message