Release early and release often is certainly the end goal. Release early does not mean releasing buggy software but limited in feature/function. But in order to release early we need to have a constant feedback loop through continuous integration and large automation test suites. I think we are not there yet and as a community we need to invest in automation first.
Thanks Animesh -----Original Message----- From: Noah Slater [mailto:nsla...@apache.org] Sent: Saturday, December 01, 2012 4:12 PM To: cloudstack-dev@incubator.apache.org Cc: David Nalley; chip.child...@sungard.com Childers Subject: Re: [DISCUSS] releases going forward 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 <rohit.ya...@citrix.com> 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 [da...@gnsa.us] > Sent: Saturday, November 10, 2012 3:37 AM > To: cloudstack-dev@incubator.apache.org > Cc: Rohit Yadav; chip.child...@sungard.com 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 > http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s04.html, > 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
