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 pranav.saxena@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Pranav Saxena <pranav.saxena@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 28 Feb 2013 23:10:07 +0530
Subject: RE: [ACS41] 4.1 branch moving to "limited updates only" after today
Thread-Topic: [ACS41] 4.1 branch moving to "limited updates only" after today
Thread-Index: Ac4V2Mmu1Bl20YryQi+GtHFI2SZ3nwAAZmDQ
Message-ID: 
 <67EF18FDCA335F489B366120481AB6C5F6BD914EBC@BANPMAILBOX01.citrite.net>
References: <20130228172605.GE17398@USLT-205755.sungardas.corp>
In-Reply-To: <20130228172605.GE17398@USLT-205755.sungardas.corp>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 .

I can definitely help to verify if the patch meant for 4.1 applies cleanly =
.

Thanks,
Pranav

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]=20
Sent: Thursday, February 28, 2013 10:56 PM
To: cloudstack-dev@incubator.apache.org
Subject: [ACS41] 4.1 branch moving to "limited updates only" after today

Everyone should know this by now, but our schedule has us shifting to a mod=
el where we limit the commits going into the 4.1 branch to a very few.

Now we have some serious bugs still outstanding, which is challenging to sa=
y the least.  That being said, I'd suggest that we don't change the plan.  =
Stabilizing the 4.1 branch should be our focus, and that means that we have=
 to be very selective about what commits go into it moving forward.

I'll ask that, as of the end of the day today, anyone with a commit that th=
ey want cherry-picked into 4.1 (or a patch, if conflicts are expected) plea=
se send an email to the list with the following tags:

[ACS41][Patch Request] - Followed by a reasonable description (or the bug I=
D).

I'll be watching the list and applying them as soon as I can.

However - I'd suggest a couple of things:

First, you need to *test* the fix.  I'd actually ask that we take this a bi=
t further than unit testing the fix.  If there's a bug reporter, give them =
the patch and have them build from 4.1 with the patch applied...
before asking to move it into the branch officially.  This does effect the =
process that the Citrix QA team is used to following, but I think it's the =
best option for us as a community.

Second, I need help ensuring that the commit to cherry-pick applies cleanly=
 to the 4.1 branch.  If you do the first thing, this should be easy...  but=
 I'll highlight this anyway.  If it's going to have conflicts, then you sho=
uld be providing a patch that already deals with the conflicts.  Patches li=
ke this should be in the email itself, or in reviewboard.

So this is what I'd *like* to see - starting tomorrow.

Objections?  Comments?  Concerns?

-chip