Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of min.chen@citrix.com designates
 66.165.176.89 as permitted sender)
From: Min Chen <min.chen@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>, Alena Prokharchyk
	<Alena.Prokharchyk@citrix.com>
CC: David Nalley <david@gnsa.us>, Rohit Yadav <bhaisaab@apache.org>
Date: Thu, 18 Apr 2013 11:15:57 -0700
Subject: Re: [ACS41] API Compatibility Bug?
Thread-Topic: [ACS41] API Compatibility Bug?
Thread-Index: Ac48YMaVvBaUgUswQ9OsVop9nSWjRA==
Message-ID: <CD958638.1C90E%min.chen@citrix.com>
In-Reply-To: <20130418180825.GG88962@USLT-205755.sungardas.corp>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I can provide a quick fix on 4.0 branch. For 4.0 branch, what is the
process to commit a fix? Submit a patch for Joe to commit, or I can
directly commit?

Thanks
-min

On 4/18/13 11:08 AM, "Chip Childers" <chip.childers@sungard.com> wrote:

>On Thu, Apr 18, 2013 at 11:07:18AM -0700, Alena Prokharchyk wrote:
>> On 4/18/13 11:02 AM, "Chip Childers" <chip.childers@sungard.com> wrote:
>>=20
>> >On Thu, Apr 18, 2013 at 10:57:51AM -0700, Alena Prokharchyk wrote:
>> >> On 4/18/13 10:48 AM, "Chip Childers" <chip.childers@sungard.com>
>>wrote:
>> >>=20
>> >> >On Thu, Apr 18, 2013 at 10:46:38AM -0700, Alena Prokharchyk wrote:
>> >> >> I would probably leave it for 4.2.0. And update the release notes
>>for
>> >> >>4.0
>> >> >>=20
>> >> >> Chip, what do you think?
>> >> >
>> >> >Doesn't 4.1 actually have the right code in it already?
>> >> >
>> >> >I think Joe is asking about the 4.0 branch, since he's about to cut
>>the
>> >> >second RC for that code line.
>> >>=20
>> >>=20
>> >> 4.1 does have correct code. Chip, would you advise to patch 4.0? It
>> >>would
>> >> require java code changes - fixing annotations in the APIs. Then we
>>have
>> >> to generate new xml/html api docs.
>> >>=20
>> >> -Alena.
>> >
>> >Joe's the RM for the 4.0.2 release.  I think he's asking about (1)
>> >impact, (2) risk and (3) how quick the fix will be.  We're about to
>> >start another round of voting for 4.0.2, and generating new API docs
>> >will be part of that release process anyway.  The question is really
>> >intended to get the code clean so that the (hopefully) last 4.0.x
>> >release has correct docs in it.
>> >
>>=20
>>=20
>> There is a minimal impact - only api docs will get affected, and the fix
>> should be relatively quick as all we have to do is to fix
>>@Implementation
>> parameter in 3 java classes.
>>=20
>>
>
>I *think* joe would love a patch for the 4.0 branch for this!