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 02BC6F460 for ; Fri, 19 Apr 2013 10:39:21 +0000 (UTC) Received: (qmail 85230 invoked by uid 500); 19 Apr 2013 10:39:20 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 85200 invoked by uid 500); 19 Apr 2013 10:39:20 -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 85180 invoked by uid 99); 19 Apr 2013 10:39:20 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Apr 2013 10:39:20 +0000 Received: from localhost (HELO [172.20.2.30]) (127.0.0.1) (smtp-auth username smarru, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Apr 2013 10:39:19 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Features for 0.8 release From: Suresh Marru In-Reply-To: Date: Fri, 19 Apr 2013 06:39:19 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <123841D0-B734-4A6C-AE58-3F281E82699C@apache.org> References: <43C627C0-CE68-45AD-B356-5AC86AE2A9CA@gmail.com> To: dev@airavata.apache.org X-Mailer: Apple Mail (2.1503) Saminda,=20 This is great to hear and since it will not be included in 0.8, we don't = need to discuss in detail now. But, once you have a prototype, before = you go too far with the full implementation, please discuss the design = on the list.=20 Raman, =20 I would still suggest to follow the release time line and not keep the = feature additions open ended through the release cycle. So please add = all improvements which needs to go into 0.8 within the first two weeks. = Lets avoid adding any new feature or API additions after this period. We = all need to work within this time line, so we can ensure the releases = happen within 6 weeks and more importantly the code is well tested.=20 Suresh On Apr 18, 2013, at 5:58 PM, Saminda Wijeratne = wrote: > Hi Lahiru,, >=20 > I'm going to work on a prototype workflow engine for Airavata. While = it > will not go in to the 0.8 release, I will be making changes in the = code to > allow future transition from current workflow interpreter to this = prototype > workflow engine to allow prototype testing (which is again not part of = 0.8 > release) without affecting any of the 0.8 functionality. >=20 > Thanks, > Saminda >=20 >=20 > On Thu, Apr 18, 2013 at 4:52 PM, Raminder Singh = wrote: >=20 >> Hi Lahiru, >>=20 >> I am working on migrating Ultrascan to Airavata. I may find bugs or >> improvements in the existing code during the process. I don't have = any new >> feature request but want to give you heads up about the changes = expected. I >> am marking most of the defects under 0.8 and will make sure to update = the >> fixed version as 0.8. I will be able to provide the list of JIRA = before the >> testing. >>=20 >> Thanks >> Raminder >>=20 >> On Apr 18, 2013, at 12:52 PM, Lahiru Gunathilake wrote: >>=20 >>> Hi Amila, >>>=20 >>> Please create Jiras for each feature and set the fixed version for = 0.8 >> and >>> please post those jira urls here. So we are good to do testing once = we >> have >>> resolved all the issue for 0.8 posted here (there are multiple 0.8 = fixed >>> version issues created sometimes back). >>>=20 >>>=20 >>> On Thu, Apr 18, 2013 at 12:49 PM, Amila Jayasekara >>> wrote: >>>=20 >>>> 1. Credential Store >>>> 2. Ability to communicate over HTTPS (Was this fixed in last = release ?) >>>> If I recall the issue, we had problems saving https URL in = registry. >>>>=20 >>> This wasn't fixed in 0.7. >>>=20 >>> Lahiru >>>=20 >>>>=20 >>>> Thanks >>>> Amila >>>>=20 >>>>=20 >>>> On Thu, Apr 18, 2013 at 10:29 AM, Lahiru Gunathilake = >>>> wrote: >>>>=20 >>>>> Hi All, >>>>>=20 >>>>> We have done the 0.7 release now, and we are trying to adapt to 6 = weeks >>>>> release cycle so this is the right time to come up with features = for >> next >>>>> release which is going to happen in 6 weeks from this week = (Tuesday). >>>>>=20 >>>>> So please come up with features you want to be there in 0.8 and >>>>> realistically which can be finished in 5 weeks (atleast) from now. = If >> you >>>>> have urgent features which you think cannot be implemented in 5 = weeks >>>>> please shoot too. >>>>>=20 >>>>> Regards >>>>> Lahiru >>>>>=20 >>>>> -- >>>>> System Analyst Programmer >>>>> PTI Lab >>>>> Indiana University >>>>>=20 >>>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> System Analyst Programmer >>> PTI Lab >>> Indiana University >>=20 >>=20