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 Chiradeep.Vittal@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Chiradeep Vittal <Chiradeep.Vittal@citrix.com>
To: CloudStack DeveloperList <cloudstack-dev@incubator.apache.org>
Date: Mon, 14 Jan 2013 10:59:59 -0800
Subject: Re: [ACS41] Concerns about where development has happened
Thread-Topic: [ACS41] Concerns about where development has happened
Thread-Index: Ac3yiVrrJlRR/oQkQhigDyb3M86fKw==
Message-ID: <CD19957F.40901%chiradeep.vittal@citrix.com>
In-Reply-To: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA3B29D5F@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I tried to do the revert for 306 myself, trying several different
strategies and I was unable to make progress.

On 1/14/13 10:55 AM, "Alex Huang" <Alex.Huang@citrix.com> wrote:

>=20
>> I thought that we had agreed that Chiradeep's network refactoring was
>> going to merge into master first, and he's waiting for the reverts
>> before doing his merge.  Alex (others), what's your opinion?
>>=20
>Chip,
>
>We've looked at the effects from the reverts on javelin.  I think the
>main problem is the commits for bug 306.  This one is particularly bad
>because its fixes are intertwined now with the api_refactoring merge and
>it's difficult to for us to see a way out of this one.  We like to ask
>the community for an exception for this bug on technical reasons for this
>one problem.  I talked with Chiradeep and he's okay with that as well for
>the network refactoring branch.
>
>If for some reason the fixes for this bug cannot pass ip clearance then
>we'll just have to deal with it.
>
>All the other reverts, we're fine with absorbing in javelin.
>
>--Alex