Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of srivatsav.prasanna@gmail.com
 designates 209.85.212.173 as permitted sender)
Sender: prasanna <srivatsav.prasanna@gmail.com>
Date: Sun, 24 Feb 2013 12:27:29 +0530
From: Prasanna Santhanam <tsp@apache.org>
To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>
Cc: Radhika Puthiyetath <radhika.puthiyetath@citrix.com>,
	Joe Brockmeier <jzb@zonker.net>, David Nalley <david@gnsa.us>,
	Jessica Tomechak <jessica.tomechak@gmail.com>
Subject: Re: Review Request: Fix for CloudStack-462. Installation Guide
 Errors Are Fixed
Message-ID: <20130224065729.GA1377@cloud-2.local>
Mail-Followup-To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>,
	Radhika Puthiyetath <radhika.puthiyetath@citrix.com>,
	Joe Brockmeier <jzb@zonker.net>, David Nalley <david@gnsa.us>,
	Jessica Tomechak <jessica.tomechak@gmail.com>
References: <20130222153554.18986.5607@reviews.apache.org>
 <20130222165417.18986.51581@reviews.apache.org>
 <97F4356AEA71904482CD192135C038F9011CC1538653@BANPMAILBOX01.citrite.net>
 <20130222170926.GH90611@USLT-205755.sungardas.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130222170926.GH90611@USLT-205755.sungardas.corp>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Fri, Feb 22, 2013 at 12:09:26PM -0500, Chip Childers wrote:
> On Fri, Feb 22, 2013 at 10:35:13PM +0530, Radhika Puthiyetath wrote:
> > What is the right process in such situation ? I have submitted the
> > patch two months back. The patch was not reviewed for long. 
> > 
> > Later some of the files are submitted to the Master, and now the
> > patch is obsolete. Should I be resubmitting the patch rebasing the
> > Master, or just abandon it ?
> 
> This sucks when it happens.  Sorry about that Radhika.

Yes - it does. Increasingly frustrating when it happens to a
contributor repeatedly. 

What we could do is poll reviewboard/cloudstack for reviews each day
and apply each of the patches in sequence on the latest HEAD available
at that time. And email the conflicts and failures to the list as a
digest, alerting of the diverging target branch. Anyone want to
automate that? I think it's doable.

We'll need a stop gap solution before convincing the ASF of gerrit
reviews. Anyone following up on that?

And how about -1 points to committers who don't get to a review done
in time? :)

/me ducks the asf brickbats
-- 
Prasanna.,