cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: [DISCUSS] releases going forward
Date Sun, 02 Dec 2012 00:12:26 GMT
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?

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
> 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
> >


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message