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 4C57E10003 for ; Wed, 18 Dec 2013 15:04:09 +0000 (UTC) Received: (qmail 74652 invoked by uid 500); 18 Dec 2013 15:02:50 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 74548 invoked by uid 500); 18 Dec 2013 15:02:48 -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 74510 invoked by uid 99); 18 Dec 2013 15:02:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Dec 2013 15:02:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of raminderjsingh@gmail.com designates 209.85.213.53 as permitted sender) Received: from [209.85.213.53] (HELO mail-yh0-f53.google.com) (209.85.213.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Dec 2013 15:02:37 +0000 Received: by mail-yh0-f53.google.com with SMTP id b20so5262423yha.26 for ; Wed, 18 Dec 2013 07:02:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=ohaReXVOIEs3PaQfHVemzFwuti2/W5a/DFyHWEOGB48=; b=U6tRMAaoKgCyOOeCCtQfzexRa5PrpJr4KR3Sj1EaLNa681X/pW6r302OUTcH8S2bht luw2H/N2PZ7PqN3Xm1xHFOJvdmUBsbdnP7SUy4B3/U9bio57J6R0h/wYxpU0VyytSjfz Uu9YOC/ukX7fjj5L3uH8QOO1DSXS8LT4VKma0FT9OHEIKIrcgXFPrujjHenHx1jk7nNs lrSKLMITC+I1YNTbV6m3MkdknPZ1hHoEMeb3sqkioVvtUobXAAwPAliXc3Qs7PpPx/4F W2uPbjQzPlb3ADhvvgto4m2z5IgC11jUNJa0HfOvRM2zd7EwBT9cIYWwc6upEFd+H7fM N0Gw== X-Received: by 10.236.15.102 with SMTP id e66mr16428805yhe.69.1387378936251; Wed, 18 Dec 2013 07:02:16 -0800 (PST) Received: from 149-160-158-107.dhcp-bl.indiana.edu ([149.160.158.107]) by mx.google.com with ESMTPSA id h66sm517423yhb.7.2013.12.18.07.02.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 07:02:14 -0800 (PST) From: Raminder Singh Content-Type: multipart/alternative; boundary="Apple-Mail=_517064D8-EDF2-44AD-95F4-C5A70C010790" Message-Id: <737944DC-9D06-45C2-BB3B-38A61A7CB8CB@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: [DISCUSS] Apache Airavata 0.11 RC1 release Date: Wed, 18 Dec 2013 10:02:12 -0500 References: To: dev@airavata.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1822) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_517064D8-EDF2-44AD-95F4-C5A70C010790 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I did testing of Gram and GSISSH providers and tested API to run jobs. I = found an issue [1] with GSISSH provider but its not a blocker. I rolled = back the Jglobus version to 2.0.6 and bouncycastle version to 1.45. I = think we are good to create RC2.=20 Thanks Raminder 1. https://issues.apache.org/jira/browse/AIRAVATA-969 On Dec 18, 2013, at 9:32 AM, Lahiru Gunathilake = wrote: > I have tested the same scenario on my big screen it worked fine, but = on my mac it gave the same issue. >=20 > Regards > Lahiru >=20 >=20 > On Wed, Dec 18, 2013 at 9:26 AM, Chathuri Wimalasena = wrote: > We encountered [1] while testing. I'm not sure whether this is a = blocker or not. Since it only comes with Mac OS, this may not a blocker. = But if you are a Mac user, you won't be able to run a workflow which has = multiple inputs from xbaya.=20 >=20 > Regards, > Chathuri >=20 > [1] https://issues.apache.org/jira/browse/AIRAVATA-971 >=20 >=20 > On Tue, Dec 17, 2013 at 3:30 PM, Saminda Wijeratne = wrote: > I'm not seeing any blockers so far with the RC1. >=20 > Did the 5/10 min tutorials > Basic descriptor and workflow tests using XBaya > Ran the client samples > Build the source distribution with tests on a clean m2 repo >=20 > Minor issue was reported via JIRA[1]. Updated the source code with the = version 0.11 for XBaya version and Airavata client version. >=20 > If no one else finds any blocker issues I think we can go for an RC2 = which would be the final build for 0.11. wdyt? >=20 > Thanks, > Saminda >=20 > 1. https://issues.apache.org/jira/browse/AIRAVATA-970=20 >=20 >=20 >=20 >=20 > On Sun, Dec 15, 2013 at 1:28 PM, Lahiru Gunathilake = wrote: >=20 > Hi Chathuri, >=20 > I think having snapshot as the version in RC is wrong. Every RC has to = be like a release and if it pass we just call a vote/discussion thread = and do the release. If we do with snapshot and if things go right, then = have to change versions and test again. But we can do the release just = by changing snapshot without testing but that wrong AFAIT. >=20 > I remember doing this mistake in earlier release with RC1 build. I = think we can stick to the release management instructions in = airavata.org. >=20 > Regards > Lahiru >=20 >=20 > On Fri, Dec 13, 2013 at 3:43 PM, Chathuri Wimalasena = wrote: > Hi All, >=20 > Airavata 0.11 RC1[1] is ready for testing.=20 >=20 > Here are some pointers for testing > Verify the fixed issue for this release [2] > Verify the basic workflow composition/execution/monitoring scenarios = from > Airavata 5 & 10 min tutorials [3],[4] > Verify airavata client samples > Verify the stability with derby & mysql backend databases > Verify that the XBaya JNLP distribution works=20 > Verify deploying Airavata server in a tomcat distribution > Please report any issues[5] if you encounter while testing. Thank you = for your time in validating the release. >=20 > Regards, > Chathuri (On behalf of Airavata PMC) >=20 > [1] https://dist.apache.org/repos/dist/dev/airavata/0.11/RC1/ > [2] = https://issues.apache.org/jira/browse/AIRAVATA-278?jql=3Dproject%20%3D%20A= IRAVATA%20AND%20fixVersion%20%3D%20%220.11%22%20ORDER%20BY%20status%20DESC= %2C%20priority%20DESC > [3] = http://airavata.apache.org/documentation/tutorials/airavata-in-5-minutes.h= tml > [4] = http://airavata.apache.org/documentation/tutorials/airavata-in-10-minutes.= html > [5] https://issues.apache.org/jira/browse/AIRAVATA >=20 >=20 >=20 >=20 >=20 >=20 > --=20 > System Analyst Programmer > PTI Lab > Indiana University >=20 >=20 >=20 >=20 >=20 > --=20 > System Analyst Programmer > PTI Lab > Indiana University --Apple-Mail=_517064D8-EDF2-44AD-95F4-C5A70C010790 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I did = testing of Gram and GSISSH providers and tested API to run jobs. I found = an issue [1] with GSISSH provider but its not a blocker. I rolled back = the Jglobus version to 2.0.6 and bouncycastle version to 1.45. I think = we are good to create = RC2. 

Thanks
Raminder

=
1. https://issues= .apache.org/jira/browse/AIRAVATA-969


<= div>
On Dec 18, 2013, at 9:32 AM, Lahiru Gunathilake <glahiru@gmail.com> = wrote:

I have tested the same scenario on my big = screen it worked fine, but on my mac it gave the same = issue.

Regards
Lahiru


On Wed, Dec 18, 2013 at 9:26 AM, Chathuri Wimalasena <kamalasini@gmail.com> = wrote:
We encountered [1] while testing. I'm not sure whether = this is a blocker or not. Since it only comes with Mac OS, this may not = a blocker. But if you are a Mac user, you won't be able to run a = workflow which has multiple inputs from xbaya. 

Regards,
Chathuri



On Tue, Dec 17, 2013 at 3:30 PM, Saminda = Wijeratne <samindaw@gmail.com> = wrote:
I'm not seeing any = blockers so far with the RC1.

Did the 5/10 min = tutorials
Basic descriptor and workflow tests using = XBaya
Ran the client samples
Build the source distribution with tests on a clean m2 = repo

Minor issue was reported via JIRA[1]. Updated the = source code with the version 0.11 for XBaya version and Airavata client = version.

If no one else finds any blocker issues I think we can go for an RC2 = which would be the final build for 0.11. = wdyt?

Thanks,
Saminda


On Sun, Dec 15, = 2013 at 1:28 PM, Lahiru Gunathilake <glahiru@gmail.com> wrote:

=
Hi Chathuri,

I = think having snapshot as the version in RC is wrong. Every RC has to be = like a release and if it pass we just call a vote/discussion thread and = do the release. If we do with snapshot  and if things go right, = then have to change versions and test again. But we can do the release = just by changing snapshot without testing but that wrong AFAIT.

=
I = remember doing this mistake in earlier release with RC1 build. I think = we can stick to the release management instructions in airavata.org.

=
Rega= rds
Lahiru


On Fri, Dec 13, 2013 at 3:43 PM, Chathuri = Wimalasena <kamalasini@gmail.com> wrote:
Hi All,

Aira= vata 0.11 RC1[1] is ready for testing. 

Here are some pointers for = testing
  • Verify the fixed issue = for this release [2]
  • Verify the basic = workflow composition/execution/monitoring scenarios = from
  • Airavata 5 & 10 min = tutorials [3],[4]
  • Verify airavata = client samples
  • Verify the stability with derby = & mysql backend databases
  • Verify that the = XBaya JNLP distribution works 
  • Verify deploying Airavata = server in a tomcat distribution
Please report any issues[5] if you encounter while = testing. Thank you for your = time in validating the release.

Regards,
Chathuri (On = behalf of Airavata PMC)

=






--
System Analyst Programmer
PTI = Lab
Indiana University





-- =
System Analyst Programmer
PTI Lab
Indiana = University

= --Apple-Mail=_517064D8-EDF2-44AD-95F4-C5A70C010790--