Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: error (athena.apache.org: local policy)
Date: Tue, 23 Apr 2013 20:30:41 +0530
From: Prasanna Santhanam <tsp@apache.org>
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.1.0 (second round)
Message-ID: <20130423150041.GA6730@cloud-2.local>
Mail-Followup-To: dev@cloudstack.apache.org
References: <20130423000432.GV4888@USLT-205755.sungardas.corp>
 <6DE00C9FDF08A34683DF71786C70EBF02F8CC419@SBPOMB402.sbp.lan>
 <20130423142039.GB2007@cloud-2.local>
 <20130423142513.GB64138@USLT-205755.sungardas.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130423142513.GB64138@USLT-205755.sungardas.corp>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Tue, Apr 23, 2013 at 10:25:13AM -0400, Chip Childers wrote:
> On Tue, Apr 23, 2013 at 07:50:39PM +0530, Prasanna Santhanam wrote:
> > On Tue, Apr 23, 2013 at 02:08:46PM +0000, Hugo Trippaers wrote:
> > > All,
> > > 
> > > -1 :-(
> > > 
> > > Found a small issue in packaging.sh. It did not work with the nonoss
> > > build and a version number without SNAPSHOT. See ticket
> > > CLOUDSTACK-2152.
> > > 
> > > Fixed with commit f9c6d01cfb90aa7c5bac5c5be20a7a16e30a9aec and
> > > df2e0108ea312e3061cd7e00d2cf4c5eaf5431fb
> > > 
> > > Cheers,
> > > 
> > > Hugo
> > 
> > Grrmph, Should we begin voting only when the following are ensured:
> > 
> > a. builds fine (oss and nonoss)
> > b. packages fine (oss and nonoss)
> > c. All jenkins jobs are stable
> 
> Yes, in fact I'm going to take a bit longer with the next round.  I want
> to do oss / nonoss builds + packaging testing on RHEL and Ubuntu.
> 

Thanks Chip - job [1] packages OSS and [2] tests the package by
configuring the server on a base rhel6.3 VM with puppet. So OSS is
taken care of for RHEL.

[1] http://jenkins.buildacloud.org/job/package-rhel63-4.1/
[2] http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-packaging/

> I do check the jenkins jobs are clear before cutting though.
> 
> What we don't see in jenkins are the issues found with removing SNAPSHOT
> from our version number, because of the way that these jobs are
> currently coded (also due to the preference stated to re-version back to
> the SNAPSHOT version in the repo as part of spinning out the RC...
> i.e.: one commit that we use to vote against that removes SNAPSHOT and
> one immediately after that reverts that change).
> 
> -chip

-- 
Prasanna.,

------------------------
Powered by BigRock.com