Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-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 7459610615 for ; Fri, 28 Feb 2014 18:46:53 +0000 (UTC) Received: (qmail 52937 invoked by uid 500); 28 Feb 2014 18:46:52 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 52857 invoked by uid 500); 28 Feb 2014 18:46:52 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 52850 invoked by uid 99); 28 Feb 2014 18:46:52 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 18:46:51 +0000 Received: from localhost (HELO 149-160-247-166.dhcp-bl.indiana.edu) (127.0.0.1) (smtp-auth username smarru, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 18:46:51 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: 0.12 release dependencies From: Suresh Marru In-Reply-To: Date: Fri, 28 Feb 2014 13:46:49 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <8BA039B7-8161-48CD-873A-DAF6EB63ED57@apache.org> References: <5310D57D.60407@iu.edu> To: Airavata Dev X-Mailer: Apple Mail (2.1874) Good point Amila, thats needs to be done too. Will you have some time before or after the release to change the sample = gateway to use the API. That will help you critique the API hands-on. Suresh On Feb 28, 2014, at 1:41 PM, Amila Jayasekara = wrote: > I assume that integration tests will be modified according to the new = API and they will be fixed.=20 >=20 > Thanks > Amila >=20 >=20 > On Fri, Feb 28, 2014 at 1:29 PM, Marlon Pierce = wrote: > Here is a summary of stuff that is needs to be wrapped up before we = have > a release candidate. I'm posting this for the record. >=20 > 1. End to end testing of Registry, Orchestrator, GFAC, and Monitoring: > Chathuri and Lahiru are committing here. >=20 > 2. GFAC Monitoring Info deposited to Registry: Raminder is working on > this. This involves GFAC changes but can go in parallel with #1. = There > is some implementation work to be done and then integration testing. >=20 > 3. Need to test the Monitoring API implementation. Chathuri will do > this. This is dependent on #3. >=20 > 4. Packaging: need to figure this out for git. Suresh is looking into = this. >=20 >=20 > Marlon >=20 >=20 >=20