Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 508AE10698 for ; Thu, 18 Apr 2013 18:09:17 +0000 (UTC) Received: (qmail 5577 invoked by uid 500); 18 Apr 2013 18:09:16 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 5536 invoked by uid 500); 18 Apr 2013 18:09:16 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 5521 invoked by uid 99); 18 Apr 2013 18:09:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 18:09:16 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [74.125.149.209] (HELO na3sys009aog113.obsmtp.com) (74.125.149.209) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 18:09:09 +0000 Received: from mail-ye0-f198.google.com ([209.85.213.198]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKUXA2nHUOW1ocBtHmlO/3bp/JpSSYibln@postini.com; Thu, 18 Apr 2013 11:08:49 PDT Received: by mail-ye0-f198.google.com with SMTP id m12so4517377yen.5 for ; Thu, 18 Apr 2013 11:08:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:x-gm-message-state; bh=cnxHKPfHFsvJXUxvT6m+S+hMVpfnF8KuIDt/4x+aZC8=; b=L6Tp1uXCK471s6HFgmsKwVq7iYXdN81p6wU1qVWIcwLGYmM1/7h+HEwcNNWHr49UJp l/oSOugsPOsoY2u7/HvMHSqB5akCsKty9Lv3bd9uK/3pC4jKpatt30uE5Jyve1RE0TJs 0D1TpzPbz3SCZWc7FID/VEtG/XgQgfw1mQsdMXkdrO8QxaVyMTtXHePHvZoTdtKwqs0x f8crSHCveR7OnI/bEOv5YqEcFZ9oFv+l3USKIuHtLmjJP01Uay8Zr6nXMdo2so8W5Kx3 CNLWuZogTgixnikM42b37YPPyzqIgYaOGPuq8YXl2NZS/zkdXjRkpnrqMQ1AvTwJFiSr B/mQ== X-Received: by 10.52.73.165 with SMTP id m5mr7821047vdv.5.1366308507869; Thu, 18 Apr 2013 11:08:27 -0700 (PDT) X-Received: by 10.52.73.165 with SMTP id m5mr7821040vdv.5.1366308507764; Thu, 18 Apr 2013 11:08:27 -0700 (PDT) Received: from localhost ([216.203.6.11]) by mx.google.com with ESMTPS id v19sm7091051vek.3.2013.04.18.11.08.26 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Apr 2013 11:08:26 -0700 (PDT) Date: Thu, 18 Apr 2013 14:08:25 -0400 From: Chip Childers To: Alena Prokharchyk Cc: "dev@cloudstack.apache.org" , David Nalley , Rohit Yadav Subject: Re: [ACS41] API Compatibility Bug? Message-ID: <20130418180825.GG88962@USLT-205755.sungardas.corp> References: <20130418180214.GF88962@USLT-205755.sungardas.corp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Gm-Message-State: ALoCoQmvSbgCwOrDpp0lD6Jcoc8R24hJdmAXXRhgESMgLjSrglILPu8ND40OVHwpSr4V0cXB6w8YOWPEL6g2CKx9hv/lPhTiGtQxbmg96B7cjS00dAs5MoIfDameHFsgdRqtBp30b33VWaNbuULQb+7rdCRBZnc7+bAXNc8T7M52EqQk1TVoN4w= X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Apr 18, 2013 at 11:07:18AM -0700, Alena Prokharchyk wrote: > On 4/18/13 11:02 AM, "Chip Childers" wrote: > > >On Thu, Apr 18, 2013 at 10:57:51AM -0700, Alena Prokharchyk wrote: > >> On 4/18/13 10:48 AM, "Chip Childers" wrote: > >> > >> >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 > >> >> > >> >> 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. > >> > >> > >> 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. > >> > >> -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. > > > > > 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. > > I *think* joe would love a patch for the 4.0 branch for this!